- Accelerated Compositing - 3D Canvas Solutions are currently pretty separate

- Accelerated 2D canvas Google's solution upstreamed (Skia/NC), still profiling Currently hybrid mode, would work better in full HW mode - not with read-backs. should canvas-2d have a "no-readback" mode or other rendering hints? Not turned on by default - correctness issues

- How does this jive with WebKit2/multi-process Chromium - a 3rd GPU process that handles all the OpenGL commands and embeds a window into the front process Qt - marshal the graphics-layer commands; RIM does something similar Apple - CA on Mac, shared-textures on Windows (not complete yet)

- Differences between ports

- GPU for regular rendering (?)

- SVG acceleration Context switching relies on GPU for regular rendering?

- 3D CSS without acceleration Makes some sense; not a huge traction.

- what's composited fixed position? should everything be render-layers? texture-limit

- is something in the acceleration/animation API layer missing animation scrubbing - mostly for authoring tools interesting area: requestAnimationFrame

- transitions/animation CSS last addition was fill-mode

- let the web developers decide? Makes sense on some level since developers do translateZ(0) and other tricks anyway. In Qt we sometimes interpret accelerated-compositing as pure software, in memory constrained environments.