Platform/GFX/Firefox.next: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
* switch away from xlib to cairo-gl and image backends on linux (note: the size of this item depends a lot on the current status of cairo-gl: how much do we need to fix it ourselves?) | * switch away from xlib to cairo-gl and image backends on linux (note: the size of this item depends a lot on the current status of cairo-gl: how much do we need to fix it ourselves?) | ||
** bjacob | ** bjacob | ||
* integrate cairo-gl for canvas on Mac and Linux (and maybe WinXP with ANGLE?) | * integrate cairo-gl (maybe just for canvas?) on Mac and Linux (and maybe WinXP with ANGLE?) | ||
** bjacob | ** bjacob | ||
** joe | |||
* themeing using GetThemeBitmap() - bug 561265 | * themeing using GetThemeBitmap() - bug 561265 | ||
* Hardware accelerated plugin layers on windows | * Hardware accelerated plugin layers on windows |
Revision as of 20:25, 4 November 2010
Lower fruit
- Improve video performance - profiling and fixing problems
- better qcms ICCv4 support
- jrmuizel
- CSS 3D transforms
- bjacob
Medium sized
- border support in layers (9 part layers) - this should let us hardware accelerate border type effects better
- cairo-gstate-backend for quartz and D2D
- accelerated layers on linux
- bjacob
- switch away from xlib to cairo-gl and image backends on linux (note: the size of this item depends a lot on the current status of cairo-gl: how much do we need to fix it ourselves?)
- bjacob
- integrate cairo-gl (maybe just for canvas?) on Mac and Linux (and maybe WinXP with ANGLE?)
- bjacob
- joe
- themeing using GetThemeBitmap() - bug 561265
- Hardware accelerated plugin layers on windows
- Layerize all remaining containers, namely SVG mask/clip-path/filters
- Component alpha rendering using white and black source surfaces (if we don't get it into FF4)
- Multiple content processes feeding layer trees to a separate compositing process
- bjacob (if other people join!)
- Animation of layer properties offloaded to the compositing process
- any WebGL work that would not make it into 4.0 (optimizations, still-in-flux parts of the spec such as color correction, lost-context events, using ARB_robustness...?)
- bjacob
Things that would be nice
- software rasterizer tuning - we could probably use a quick and dirty rasterizer for mobile where the pixels are small