Confirmed users
1,067
edits
Platform/GFX/HardwareAcceleration/PathToFirefox4: Difference between revisions
Jump to navigation
Jump to search
Platform/GFX/HardwareAcceleration/PathToFirefox4 (view source)
Revision as of 20:32, 12 August 2010
, 12 August 2010no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
We need Firefox 4 to be hardware accelerated using OpenGL and Direct3D 9 for layers, and Direct2D for Cairo. | We need Firefox 4 to be hardware accelerated using OpenGL and Direct3D 9 for layers, and Direct2D for Cairo. | ||
= Proposed Plan = | |||
* Phase 1: Focus first on getting D3D9+D2D reftests passing. During this week and a half or so, Vlad and Benoit will focus on WebGL, and coordinate d3d work, after that, Benoit can help out on the OpenGL work. | |||
* Phase 2: Enable D3D+D2D on m-c, even without the blocklist done, even if we don't get the test pilot survey done, but we need to provide people with a way to tell us what hardware they are running if they experience issues, put that in about:support. | |||
* Phase 3: Make sure D3D9 works without D2D - Once we get here, we should be ready to go with hardware acceleration on windows, both compositing and accelerated content. | |||
* Phase 4: Shift everyone over to OpenGL. Make layers acceleration work first on the Mac. | |||
* Phase 5: Shift everyone over to Mobile: Android and Maemo. Bring in Blassy and Michael Wu. | |||
Other Issues: | |||
* Bas should fly out as soon as we have reftest issues tracked in order to sprint. | |||
* Drop libjpeg-turbo? | |||
* Drop OpenGL on Linux? Can mgregan do this? Can distros help here? | |||
* Matt Woodrow? Karlt? | |||
* Are there other little features here and there that people are working on? If so, we should probably drop. | |||
= General = | = General = | ||