CSS 3D transforms are an emerging W3C spec. WebKit has the hooks for supporting CSS 3D, but a WebKit port like Chrome still needs to add an underlying scene gra

CSS 3D transforms are an emerging W3C spec. WebKit has the hooks for supporting CSS 3D, but a WebKit port like Chrome still needs to add an underlying scene graph engine ala Core Animation to get 3D rendering going. It's non-trivial, but possible. Scene graph engines are hard to build, much like vector graphics engines and font rendering engines. That said, Clutter ToolKit (the same one Chrome OS is using for its windowing manager) is about the closest open source ready-to-go replacement that can do 80% of what is needed by WebKit to do CSS 3D on top of OpenGL. It's on Google's list to add to Chrome, but not for awhile. Google seems to be favoring WebGL over CSS 3D (too much detail to discuss pros, cons, and the politics here), and is making WebGL implementation a higher priority for now.