Big thanks to bjacob will-change[1] has now landed for privileged app. This CSS property will eventually ship for web content in gecko and in blink[2].
There's already several use of will-change in gaia[3] that will help with important animations that were difficult/impossible for the platform to predicts without nasty hacks to hint. This means that we should see improved animation performance, cpu time reduction (and negligible power savings) in b2g 1.4. For now will-change is unconditionally honored by the platform. Until that is resolved *overuse of will-change will cause out of memory errors*. We will be fixing this and preparing some dev-docs and best practices for this feature. Until then if you have any questions please f?benwa/r?benwa on patches that introduce will-change. For now the general, overly simplified, rule is avoid having more then 2-3 will-change elements at once to avoid OOM on low memory devices. [1] http://tabatkins.github.io/specs/css-will-change/ [2] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/M62y2nKZ-gE [3] http://mxr.mozilla.org/gaia/search?string=will-change _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
