|Accelerated layers on mobile via OpenGL ES|
|Release target||Firefox 10|
|Status note||Working pretty well, still has some bugs. Still looking for better performance numbers. Anecdote - scrolling is better, still work to do though.|
|Product manager||Chris Blizzard|
|Directly Responsible Individual||JPR|
|Lead engineer||Florian Hänel, Benoit Jacob|
|QA lead||Andreea Pod|
|Product marketing lead||`|
Stage 1: Definition
1. Feature overview
2. Users & use cases
- Hardware accelerate the composition of layers generated in the content process in the chrome process using OpenGL ES.
- Speed up the browsing experience for users.
- Support at least two of the following handsets by default: Nexus One; Nexus S/Galaxy S; Droid Pro; Atrix.
- "Support by default" means that GLES-composited layers is turned on by default on a handset, that it has a performance benefit, and does not overly negatively affect stability.
- GLES composition of layers should be turned on via a whitelist rather than a blacklist, because of too many driver/stability issues.
- Cross-process WebGL.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
- bug 607684 Tracking bug for OpenGL on mobile
Florian Hänel has been working on completing the layers implementation, mostly on Maemo. Benoit Jacob is getting OpenGL ES up and running on the Nexus S. Florian, Benoit, and Joe Drew will be collaborating on completing the GLES layers implementation.
- Get GLES layer composition working on the Nexus S without generating GL errors with normal browsing.
- Start running reftests, and solve the issues reftests find.
- Iterate these steps for each handset.
- Test these more generally on users' handsets, and solve issues that come up.
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
|Secondary roadmap||Firefox Mobile|
Team status notes
|Security||sec-review-active||needs fuzzing, mobile fuzzing research needed : Jesse|