Starting with the most recent builds, chromium now supports gpu-accelerated compositing and webkit's 3D CSS transforms. The code has been under development for a little while but until yesterday it was hidden behind a compile time flag. It's now being compiled in by default on Windows and gets activated when you supply:
--enable-accelerated-compositing at the command line when starting chrome. Give it a try and see how it works for you. Here's a couple of links to convince yourself that it works: http://webkit.org/blog/386/3d-transforms/ (try out all the individual demos linked from the page) http://www.satine.org/research/webkit/snowleopard/snowstack.html If you really want to be sure you're activating the accelerated compositing path, also use the: --show-composited-layer-borders flag which will add red and yellow borders around layers that are composited on the gpu. A couple of caveats: 1. The code is still pretty fresh so you will find some rough edges. Please file bugs. 2. It only works on windows (the other two platforms are coming soon). 3. You need a gpu and drivers that support at least OpenGL 2.0 . If you have a fairly recent graphics card and up-to-date drivers you should be ok. The eventual plan for Windows is to run this with D3D9 via ANGLE ( http://code.google.com/p/angleproject/). 4. WebGL and video don't currently work when accelerated compositing is enabled. It's worth noting that gpu acceleration kicks in under a fairly restricted set of conditions (as defined in common webkit code inside RenderLayerCompositor::requiresCompositingLayer()). 3D transforms and animated opacity are the most common ways to flip the switch so a quick and dirty way to force compositing on is to add a: -webkit-transform: translateZ(0) CSS property to an element. YMMV. Give it a whirl and see how it works for you. Cheers, Vangelis -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
