Re: Enabling Pointer Events in Firefox (desktop) Nightly on Mac and Linux

David Baron於 2017年4月5日星期三 UTC+8下午12時21分30秒寫道： > The dependency trees of these bugs seem like they could use somewhat > better organization, so that people can see what issues are > remaining when evaluating whether enabling on nightly is > appropriate. > > For example, if bug 1352278 and bug

Re: Intent to change editor newline behavior

On 4/5/17 9:12 AM, Ehsan Akhgari wrote:> On Tue, Apr 4, 2017 at 11:31 AM, Aryeh Gregor > wrote: > > On Tue, Apr 4, 2017 at 5:57 PM, Ehsan Akhgari > > wrote: > > I don't own this module

Re: Enabling Pointer Events in Firefox (desktop) Nightly on Mac and Linux

On Tuesday 2017-04-04 20:29 -0700, stone123...@gmail.com wrote: > We plan to enable Pointer Events for mouse, touch and pen input in Firefox > Nightly builds (on Mac and Linux) within the next few weeks. > > Related Bugs: > Bug 960316 - Enable W3C Pointer Events and touch-action CSS property

Enabling Pointer Events in Firefox (desktop) Nightly on Mac and Linux

We plan to enable Pointer Events for mouse, touch and pen input in Firefox Nightly builds (on Mac and Linux) within the next few weeks. Related Bugs: Bug 960316 - Enable W3C Pointer Events and touch-action CSS property by default Bug 1352278 - [Pointer Event] Turn on PointerEvent preference on

Re: Intent to change editor newline behavior

On Tue, Apr 4, 2017 at 8:12 PM, Ehsan Akhgari wrote: > I doubt it's used much. My assumption is only that not many sites are >> UA-sniffing Firefox, finding the s, and modifying them in some way >> that breaks if they're no longer s. That could still be totally >>

Re: Intent to change editor newline behavior

On Tue, Apr 4, 2017 at 11:31 AM, Aryeh Gregor wrote: > On Tue, Apr 4, 2017 at 5:57 PM, Ehsan Akhgari > wrote: > > I don't own this module any more, so this isn't my call to make, but if > > I had to choose what to do here, I would probably either choose

e10s-multi on Aurora

Hey all, We recently enabled 4 content processes by default on Aurora. We're still tracking several bugs that we are planning to fix in the near future as well as getting more memory measurements in Telemetry as we look towards a staged rollout in Beta and beyond. We were able to turn on in

Re: Intent to change editor newline behavior

On Tue, Apr 4, 2017 at 5:57 PM, Ehsan Akhgari wrote: > I don't own this module any more, so this isn't my call to make, but if > I had to choose what to do here, I would probably either choose to not > change our behavior (since I'm not sure what we're gaining here >

Re: Intent to change editor newline behavior

On 2017-04-04 7:55 AM, Aryeh Gregor wrote: > On Mon, Apr 3, 2017 at 11:39 PM, Benjamin Smedberg > wrote: >> >> I'd like to encourage you to set up a test plan for this. My impression of >> the risk profile of this work is that we could easily break some really >>

Re: Intent to change editor newline behavior

On Mon, Apr 3, 2017 at 11:39 PM, Benjamin Smedberg wrote: > > I'd like to encourage you to set up a test plan for this. My impression of > the risk profile of this work is that we could easily break some really > important use-cases, and it's likely that sites customize

Sheriff Highlights and Summary in March 2017 (and even Q1 2017)

Hi, We will be more active in 2017 and inform more about whats happening in Sheriffing and since its already April..lets go :) The Paid Sheriffs (kwierso and me) are now reporting to Chris Cooper (coop) and we would like to thank David Burns (Automatedtester) for his awesomeness in leading