Re: Intent to ship: CSS will-change

2014-10-31 Thread Benoit Girard
That's a good idea. Filed bug 1092320. On Fri, Oct 31, 2014 at 3:48 PM, Ehsan Akhgari wrote: > Can we make sure to log something to the web console when we choose to > dishonor will-change? That will help web developers to be able to reason > about why will-change doesn't give them the performan

Re: Intent to ship: CSS will-change

2014-10-31 Thread Ehsan Akhgari
Can we make sure to log something to the web console when we choose to dishonor will-change? That will help web developers to be able to reason about why will-change doesn't give them the performance benefits that they expect. On 2014-10-31 3:36 PM, Benoit Girard wrote: Yes, it's implemented

Re: Intent to ship: CSS will-change

2014-10-31 Thread Benoit Girard
Yes, it's implemented in part 1-4 of my patch queue in bug 961871. Here's how it works -but is subject to change at any time-: - The following are all in untransformed CSS pixel unit. This makes the implementation *much* simpler[1] and more predicable for web authors[2]. - We look at the scrollpor

Re: Intent to ship: CSS will-change

2014-10-31 Thread L. David Baron
On Friday 2014-10-31 14:17 -0400, Benoit Girard wrote: > As of next week I intend to turn will-change on by default on all > platform. It has been developed behind the > layout.css.will-change.enabled;true preference since Firefox 31 and > has been enabled for certified FirefoxOS apps since 1.4[1]

Intent to ship: CSS will-change

2014-10-31 Thread Benoit Girard
As of next week I intend to turn will-change on by default on all platform. It has been developed behind the layout.css.will-change.enabled;true preference since Firefox 31 and has been enabled for certified FirefoxOS apps since 1.4[1] [2]. Blink has already shipped this [3], IE lists the feature a