Re: Try syntax is no longer required when pushing to try

2016-03-04 Thread Armen Zambrano G.
On 16-03-03 08:35 PM, Xidorn Quan wrote: > On Fri, Mar 4, 2016 at 1:25 AM, Andrew Halberstadt > wrote: > >> With treeherder's "Add New Jobs" [1] UI, using try syntax is no longer >> the only way to schedule stuff on try. As of now, it's possible to push >> to try

Re: Try syntax is no longer required when pushing to try

2016-03-04 Thread Armen Zambrano G.
On 16-03-04 01:22 AM, Mike Hommey wrote: > On Thu, Mar 03, 2016 at 12:25:53PM -0500, Andrew Halberstadt wrote: >> With treeherder's "Add New Jobs" [1] UI, using try syntax is no longer >> the only way to schedule stuff on try. As of now, it's possible to push >> to try without any try syntax. If

Re: Intent to ship: Support for color-adjust CSS property

2016-03-04 Thread Lawrence Mandel
Whether or not we ship with the feature enabled, the ability to disable a feature with a pref gives us an easy out if a critical issue is discovered. (For ex, a code path that results in a top crash.) I suggest that we create the pref in either case and plan to remove it after a couple of releases

Intent to ship: Support for color-adjust CSS property

2016-03-04 Thread Tobias Schneider
As of Firefox 47 I intend to ship support for color-adjust on all platforms. Chrome is already shipping this as -webkit-print-color-adjust. The color-adjust CSS property allow pages to opt in to printing background colors and images. Chrome is already shipping this and Google Docs is using it in

Re: Status Notifications for New Bugs in DOM, DevTools, and Hello

2016-03-04 Thread Ted Mielczarek
On Fri, Mar 4, 2016, at 07:48 AM, Philip Chee wrote: > On 01/03/2016 03:25, Emma Humphries wrote: > > > With the help of dedicated triage teams for each component, starting this > > week when you file a bug against the DOM, Developer Tools, or Hello in > > Bugzilla you’ll receive an email

Re: Status Notifications for New Bugs in DOM, DevTools, and Hello

2016-03-04 Thread Philip Chee
On 01/03/2016 03:25, Emma Humphries wrote: > With the help of dedicated triage teams for each component, starting this > week when you file a bug against the DOM, Developer Tools, or Hello in > Bugzilla you’ll receive an email explaining the next steps in your bug’s > life. I've been

Re: SharedArrayBuffer and Atomics will ride the trains behind a pref

2016-03-04 Thread Lars Hansen
I hope I didn't suggest that people should stop discussing it; all I wanted to do was to lay out the background for the debate and the evidence that has been presented so far, in particular given Richard's strong assertions about what this attack is able to do in JS, in a browser - which in truth

Re: SharedArrayBuffer and Atomics will ride the trains behind a pref

2016-03-04 Thread Eric Rescorla
On Thu, Mar 3, 2016 at 11:39 PM, Lars Hansen wrote: > On Fri, Mar 4, 2016 at 1:41 AM, Richard Barnes > wrote: > > > Another good reason for blocking this for now is that it lets Javascript > > circumvent the 5usec granularity of performance.now() and do