From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Accelerated layers on mobile via OpenGL ES
Stage Development
Status In progress
Release target Firefox 10
Health OK
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
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead Andreea Pod
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


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.

3. Dependencies


4. Requirements

  • 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


8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review

Operations review


Stage 4: Development

9. Implementation

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.

Next Steps

  • 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


Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap Platform
Secondary roadmap Firefox Mobile
Feature list Mobile
Project Responsiveness
Engineering team Graphics

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-active needs fuzzing, mobile fuzzing research needed : Jesse
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `