Using them in the CSS style sheet is perfectly reasonable. Here's how b2g/ffos uses them carefully to make the most of low end hardware: http://mxr.mozilla.org/

Using them in the CSS style sheet is perfectly reasonable. Here's how b2g/ffos uses them carefully to make the most of low end hardware: http://mxr.mozilla.org/gaia/search?string=will-change http://mxr.mozilla.org/gaia/search?string=will-change Imagine you're writing something that does fullscreen page flips in a native app vs. a web app. An example is the android homescreen vs the ffos homescreen but I see web pages that often have a similar effect. * In a native app you're going to have to decompose your page into texture that you will animate (your widget toolkit will likely make this easier). * Without will-change you're going to hope that the rendering engine will infer your animations in a reasonable amount of time getting bad performance while you wait and hope that it doesn't fall off that optimization path. * With will-change on the b2g homescreen we just have to add a one line change.