Re: W3C Proposed Recommendation: HTML 5.1

For the record, I have reviewed the HTML5.1 changes: https://www.w3.org/TR/2016/PR-html51-20160915/changes.html#changes which are in themselves not the easiest to review, filed this accordingly: https://github.com/w3c/html/issues/592 In addition to that editorial request, the one technically obj

Coming soon to Treeherder: Duplicate Job Toggle

tl;dr: Adding a show/hide “Duplicates” button for exposing or aggregating-to-counts duplicate jobs. This is a fix to bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1234648 We currently default to aggregating (in the “+32" style groupin

Re: W3C Proposed Recommendation: HTML 5.1

On Wednesday 2016-10-12 11:22 -0400, Chris Hutten-Czapski wrote: > Can you provide any details (either inline, or a sampling of links) to > summarize the broader concerns that might not be encapsulated in the > document itself? Some links: https://annevankesteren.nl/2016/01/film-at-11 https://gith

Hardware to reproduce bug

Does anyone have hardware that might reproduce bug https://bugzilla.mozilla.org/show_bug.cgi?id=1306752? Lenovo ThinkpadL430, Elantech driver 11.4.30.3 is specified in the bug. But any Elantech touchpad might be affected. If you can reproduce the bug, please post comment to bug 1306752. Thank

Re: Triage Plan for Firefox Components

On Fri, Oct 7, 2016 at 2:29 AM, wrote: > Hi I'm someone who is studying the triage process and workflow among OSS, > Can anyone tell me does the new triage plan discussed here get adopted and > what is the final version? I would also love to know where and could I > follow your discussions on pol

Re: [Firefox Desktop] Issues found: October 3rd to October 7

Hi Amos, Thank you for sharing the issue that you're having with Firefox. We'll need a bug on file to flush out more details get traction on this. Have you filed a bug already? If not, can you please do so? https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=General Lawrence On

Intent to ship: Selection events

As of Firefox 52, I'm planning to let the selection events API < http://w3c.github.io/selection-api/#user-interactions> ride the trains on all platforms. This feature has been implemented and enabled on Nightly behind the dom.select_events.enabled pref since September last year. Blink, WebKit and

Re: Perfherder is currently broken

Update: I have a fix applied for new data ingestion, but existing results are still somewhat busted. It will take some time for a cleanup script to work through the existing data (maybe a day?) but meanwhile (new results) from try should be sane, so if you were waiting on this to push some talos

Re: Proposed W3C Charter: Web of Things Working Group

+1 on keeping w3c charter discussions here (or at least letting those of us organizational friends of Moz know where we go for that part of our Moz fix) On Thu, Oct 13, 2016 at 6:11 AM, Anne van Kesteren wrote: > On Thu, Oct 13, 2016 at 1:18 PM, Benjamin Francis > wrote: >> dev-platform is now

Re: Proposed W3C Charter: Web of Things Working Group

On Thu, Oct 13, 2016 at 1:18 PM, Benjamin Francis wrote: > dev-platform is now only really about the back end of Firefox which isn't > very relevant here. WoT mainly concerns the server side of the web stack. I don't really agree with this. 1) We can't really consider Firefox frontend and backend

Re: Proposed W3C Charter: Web of Things Working Group

On 13 October 2016 at 01:51, Martin Thomson wrote: > I agree with this sentiment, but I don't think that we need to insist > that a new W3C group solve these issues. I'm very much concerned with > the question of how a new "thing" might be authenticated, even how > clients of the thing are authe

Re: Intent to ship: css multi-column properties (unprefixed)

On Wednesday 2016-10-12 22:41 -0700, jensimm...@gmail.com wrote: > I would recommend that we ship support for column-span before we unprefix > column. Shipping only part of a specification like this is risky for interop > and web compat. Let's get all of it working behind a prefix, and then > un