WebKit Animation Performance
Lately I have been dabbling in web animations created using the WebKit Animation and WebKit Transition CSS properties. For the uninitiated, WebKit is the engine that powers Apple’s Safari web browser and Google’s Chrome browser. The Animation and Transition properties are the WebKit team’s proposed properties for creating rich online animation using only CSS.
More information on using these CSS Properties is available in the Safari Reference Library.
The benefits of animating this way are: no reliance on Flash or other browser plugins, exists in the CSS presentation layer so everything degrades nicely for browsers that don’t know how to handle it, and extremely simple syntax for attaching animations to things like adding a class or hovering an element.
That’s all well and good, of course. But this means nothing if performance is terrible. I have read complaints that WebKit animation is as much of a CPU hog as Flash, so I decided to do some simple experimentation.