At this point we're leaning towards exposing it to all of b2g however I don't expect this property to be widely used outside of gaia. We have 3 options, (1) Wait until the spec is ready and miss out on important performance improvements (2) Expose it to subset of B2G which will gain preferential treatment, (3) Expose it to all of b2g. Frankly I think (3) is the preferred option. But of course I'd like to hear feedback on it.
On Tue, Dec 3, 2013 at 5:53 PM, Ehsan Akhgari <[email protected]>wrote: > On 12/3/2013, 4:25 PM, Benoit Girard wrote: > >> In bug 940842 I started investigating adding a new CSS property >> 'will-animate' to let authors give better descriptions of their intents >> instead of relying on our complicated, and unpredictable, internal >> heuristics. The better the platform can understand what the page is trying >> to do, the better it can optimize. This has the results that the page >> behave more like a native app would from the perspective of the hardware >> and GPU. I'm glossing over a lot of details here. If you want more >> information or would like to comment on that proposal please see bug >> 940842 >> and the www-style discussion[1]. >> >> For those interested this proposal is going to be a contributing factor to >> 'performance polish' and battery. Namely when our average FPS is near >> 55-60, we can drop 5 sequential frames briefly preparing an animation. >> >> I'd like some feedback on enabling this CSS property for B2G only. I plan >> on landing this property behind a preference but setting this preference >> for B2G by default so that gaia can use it. Once the spec is accepted I >> will enable this everywhere >> > > Are you talking about exposing this to some types of apps or to web > content on b2g? I think we should definitely not expose it to web content. > > Cheers, > Ehsan > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
