This is a bad idea - forcing every DOM node to become a hardware accelerated layer is going to introduce a huge amount of memory overhead (webkit doesn't release composited layers when they scroll off screen, in many cases)
A better approach is to apply -webkit-transform: translate3d(0, 0, 0) to only those nodes that will animate.
Your mobile viewers, especially, will be glad that your page doesn't kill the browser (when it goes OOM)
A better approach is to apply -webkit-transform: translate3d(0, 0, 0) to only those nodes that will animate.
Your mobile viewers, especially, will be glad that your page doesn't kill the browser (when it goes OOM)