Platform/2010-Q3-Goals: Difference between revisions
< Platform
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
=== General Goals === | === General Goals === | ||
* {{ok|Javascript performance near or even with Chrome on their benchmarks (within | * {{ok|Javascript performance near or even with Chrome on their benchmarks (within 20% on SS, 30% on V8), with substantial wins on our benchmarks. (Windows, in-browser.)}} | ||
* {{ok|Hardware acceleration of video and other HTML and SVG content, as well as user interface, on by default for compatible hardware on all Tier-1 desktop and mobile platforms.}} | * {{ok|Hardware acceleration of video and other HTML and SVG content, as well as user interface, on by default for compatible hardware on all Tier-1 desktop and mobile platforms.}} | ||
* {{ok|Fully support the WebGL 1.0 spec, with support turned on by default in a Firefox 4 beta on platforms that support OpenGL or OpenGL ES. }} | * {{ok|Fully support the WebGL 1.0 spec, with support turned on by default in a Firefox 4 beta on platforms that support OpenGL or OpenGL ES. }} |
Revision as of 15:49, 23 June 2010
General Goals
- [ON TRACK] Javascript performance near or even with Chrome on their benchmarks (within 20% on SS, 30% on V8), with substantial wins on our benchmarks. (Windows, in-browser.)
- [ON TRACK] Hardware acceleration of video and other HTML and SVG content, as well as user interface, on by default for compatible hardware on all Tier-1 desktop and mobile platforms.
- [ON TRACK] Fully support the WebGL 1.0 spec, with support turned on by default in a Firefox 4 beta on platforms that support OpenGL or OpenGL ES.
- [ON TRACK] security: zero reproducible high/crit > 30 days
- [ON TRACK] Support multi-process Fennec.
- [ON TRACK] Support Jetpacks running in separate processes and never blocking the Fennec UI.
GFX
- Accelerate Firefox's in-content video and other content primitives by shipping, in a Firefox 4 beta, layers acceleration for the full Firefox window, on by default for compatible hardware on all tier-1 platforms, based on Direct3D 9, OpenGL, and OpenGL ES.
- Accelerate all drawing on Windows Vista and Windows 7, on compatible hardware, by shipping the Direct2D Cairo backend in a Firefox 4 beta.
- Enhance our OpenType font feature support by shipping Harfbuzz on by default in a Firefox 4 beta on all Tier-1 platforms, with text rendering performance equal to or better than Firefox 3.6.
- Fully support the WebGL 1.0 spec, with support turned on by default in a Firefox 4 beta on platforms that support OpenGL or OpenGL ES.
- Stretch goal: Also support WebGL on Direct3D via ANGLE.
Layout
- Land CSS3 calc()
- Finish and land CSS Transitions
- Land retained layers
- Land content/chrome rendering integration (bug 130078)
- Land CSS control of lowlevel font features
Video/Audio
- Support 'buffered' attribute for all media types
- Ship WebM with performance and stability equal or better than Flash on Youtube
- Contribute activity masking to VP8 encoder
Content
- [ON TRACK] Produce clear plans for accelerated windowless plugin rending on Windows and Linux (including mobile).
- [ON TRACK] Be prepared to ship OOPP for Mac OS X.
- [ON TRACK] Eliminate enablePrivilege() ("UniversalXPConnect" etc).
- [ON TRACK] Close the performance gap between Firefox and Chrome on the "Click Preferences *" tests in the Zimbra performance test harness, 30+% speedup from end of Q2.
- [ON TRACK] Finish up indexGetter/Setter work for faster list[n] access in JS
- [ON TRACK] Solidify a long term plan for the future of our DOM bindings (i.e. keep hacking on XPConnect or move over to proxies)
Privacy
- [ON TRACK] Improve user privacy by reducing the ability of sites to fingerprint individual users, and improve user control and privacy of cookies.
JS
- Performance goals for reference system: Dell Optiplex 760 (Intel Core2 Duo) Windows Vista. Baseline: Chrome 5.0.375.55.
- [ON TRACK] SunSpider: 300-375ms.
- [ON TRACK] V8 Score: 3500-5000.
- [ON TRACK] JSNES: 60fps.
Accessibility
- [ON TRACK] Provide accessibility support for existing and new HTML5 input controls.
- [ON TRACK] Reduce the a11y performance hit by at least 50% for tools that require only limited accessibility support.
- [ON TRACK] Improve/fix life cycle management of our (node and frame based) accessible objects.
Multi-Process
- [ON TRACK] This is a shiny goal.