Re: PSA: Cancel your old Try pushes

2016-04-17 Thread Steve Fink
That's a very good point about keeping the treeherder page open eating resources. I guess I've found that (1) my personal try push page takes much, much longer to get overloaded than eg the inbound page (or worse, the *full* try page); and (2) Firefox is so flaky on me for other reasons that I

Re: PSA: Cancel your old Try pushes

2016-04-17 Thread Mike Conley
If I had to guess, I'd say that it's just consuming more and more memory as more and more nodes are getting added to the DOM, and more AngularJS stuff gets instantiated. I would put good money on those multi-second pauses being attempts to GC / CC On 16 April 2016 at 05:50, Gijs Kruitbosch wrot

Re: PSA: Cancel your old Try pushes

2016-04-17 Thread Mike Conley
> Generally speaking, Firefox's stability has not been good for me for 2-3 months. I'd like to file a bug, > but I've already used up my quota of unactionable bugs, and if I dug into all of my idiosyncratic > issues I'd never get any work done. I seem to do things differently, in some problematic w

Re: Intent to ship: Treat cookies set over non-secure HTTP as session cookies

2016-04-17 Thread Chris Peterson
On 4/15/16 2:12 AM, Jason Duell wrote: > Focusing on third-party session cookies is an interesting idea. > "Sessionizing" non-HTTPS third-party cookies would encourage ad networks > and CDNs to use HTTPS, allowing content sites to use HTTPS without mixed > content problems. Much later, we could c

Re: PSA: Cancel your old Try pushes

2016-04-17 Thread Kartikaya Gupta
On Apr 17, 2016 1:55 PM, "Steve Fink" wrote: > > Generally speaking, Firefox's stability has not been good for me for 2-3 months. I'd like to file a bug, but I've already used up my quota of unactionable bugs, and if I dug into all of my idiosyncratic issues I'd never get any work done. Also (and

Stability

2016-04-17 Thread Nicholas Nethercote
On Mon, Apr 18, 2016 at 10:34 AM, Kartikaya Gupta wrote: > > My view is that if we have a lot of bugs and regressions, time spent > investigating and fixing those naturally acts as a backflow to new feature > work, which prevents the introduction of even more bugs and regressions. So > really time

Intent to ship: Element.animate

2016-04-17 Thread Brian Birtles
In Firefox 48 I intend to turn Element.animate on by default. We have been developing the Web Animations API behind the dom.animations-api.core.enabled preference and have introduced the dom.animations-api.element-api.enabled preference for the subset of the API that we intend to ship at this

Re: Intent to ship: Element.animate

2016-04-17 Thread Anne van Kesteren
On Mon, Apr 18, 2016 at 4:12 AM, Brian Birtles wrote: > We do not intend to > ship the 'finished' promise at this time due to concern that this should use > a cancelable promise. \o/ -- https://annevankesteren.nl/ ___ dev-platform mailing list dev-pl