Platform/Features/GLESAcceleratedLayers: Difference between revisions

no edit summary
No edit summary
 
(10 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{| class="fullwidth-table"
{{FeatureStatus
|-
|Feature name=Accelerated layers on mobile via OpenGL ES
| style="font-weight: bold; background: #DDD;" | Feature
|Feature stage=Development
| style="font-weight: bold; background: #DDD;" | Status
|Feature status=In progress
| style="font-weight: bold; background: #DDD;" | ETA
|Feature version=Firefox 10
| style="font-weight: bold; background: #DDD;" | Owner
|Feature health=OK
|-
|Feature status note=Working pretty well, still has some bugs.  Still looking for better performance numbers.  Anecdote - scrolling is better, still work to do though.
<section begin="status" />
}}
| [[Platform/Features/GLESAcceleratedLayers|Accelerated layers on mobile via OpenGL ES]]
{{FeatureTeam
| {{StatusHealthy|status=being actively worked}}
|Feature product manager=Chris Blizzard
| unknown
|Feature feature manager=JPR
| Stuart Parmenter
|Feature lead engineer=Florian Hänel, Benoit Jacob
<section end="status" />
|Feature qa lead=Andreea Pod
|-
}}
|}
{{FeaturePageBody
 
|Feature users and use cases=* Hardware accelerate the composition of layers generated in the content process in the chrome process using OpenGL ES.
== Summary ==
* Speed up the browsing experience for users.
For greater performance, layers need to be composited using the GPU on mobile, leading to a better user experience and (probably) less battery usage.
|Feature 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.
We need to finish the OpenGL ES layers backend and get it working on multiple handsets.  
** GLES composition of layers should be turned on via a whitelist rather than a blacklist, because of too many driver/stability issues.
 
|Feature non-goals=* Cross-process WebGL.
== Team ==
|Feature qa review=* [[Fennec/Features/GLESAcceleratedLayers/testplan]]
Who's working on this?
|Feature implementation notes=* {{bug|607684}} Tracking bug for OpenGL on mobile
 
* '''Lead Developer''': Benoit Jacob
* '''Product Manager''': Chris Blizzard
* '''QA''': unknown
* '''Security''': unknown; necessary?


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.
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.


== Release Requirements ==
==== Next Steps ====
* 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.
 
== Next Steps ==
* Get GLES layer composition working on the Nexus S without generating GL errors with normal browsing.
* 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.
* Start running reftests, and solve the issues reftests find.
Line 41: Line 31:
* Test these more generally on users' handsets, and solve issues that come up.
* Test these more generally on users' handsets, and solve issues that come up.


== Related Bugs & Dependencies ==
* [[Platform/GFX/GLLayersOnMobile|Status report on requirements for GL layers on mobile]]
* {{bug|607684}} Tracking bug for OpenGL on mobile
}}
 
{{FeatureInfo
== Designs ==
|Feature priority=P1
None listed.
|Feature roadmap=Platform
 
|Feature secondary roadmap=Firefox Mobile
== Goals/Use Cases ==
|Feature list=Mobile
* Hardware accelerate the composition of layers generated in the content process in the chrome process using OpenGL ES.
|Feature project=Responsiveness
* Speed up the browsing experience for users.
|Feature engineering team=Graphics
 
}}
== Non-Goals ==
{{FeatureTeamStatus
* Cross-process WebGL.
|Feature security status=sec-review-active
 
|Feature security health=Assigned
== Other Documentation ==
|Feature security notes=needs fuzzing, mobile fuzzing research needed : Jesse
[[Platform/GFX/GLLayersOnMobile|Status report on requirements for GL layers on mobile]]
}}
 
== Legend (remove if you like) ==
{| class="fullwidth-table"
|-
| {{StatusHealthy|status=&nbsp;}}
| Healthy: feature is progressing as expected.
|-
| {{StatusBlocked|status=&nbsp;}}
| Blocked: feature is currently blocked, but not yet at risk of missing this release.
|-
| {{StatusAtRisk|status=&nbsp;}}
| At Risk: feature is at risk of missing this release.
|-  
| '''ETA'''
| Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.
|}
 
__NOTOC__
 
Please remove this line and any non-relevant categories below.  Add whatever other categories you feel are appropriate.
 
[[Category:Features]]
[[Category:Firefox]]
[[Category:Performance]]
[[Category:Polish]]
[[Category:Priority 1]]
[[Category:Priority 2]]
[[Category:Priority 3]]
[[Category:Unprioritized]]
1,148

edits