WebRender Planning
Here is a highlevel breakdown of the WebRender roadmap for 2019: https://github.com/orgs/FirefoxGraphics/projects/1
(Note: we are currently working on revamping this to represent a high-level for 2020)
This document is a more detailed view of that roadmap, including burnup charts. Also tracking core pieces of work here: https://github.com/orgs/FirefoxGraphics/projects/4
For a list of the various places we have shipped WebRender, see: https://wiki.mozilla.org/Platform/GFX/WebRender_Where
Under 'compositor usage' you can see the % of Windows users who are using WebRender: https://firefoxgraphics.github.io/telemetry/#view=windows-features
Q4 Priorities for WR
The priorities for Q4 (October/November/December) 2019
- Ship our WebRender targets for 70 and 71
- The target for 70 is Windows 10 desktop Intel, with low res screens
- The target for 71 is Windows 10 laptop Nvidia, with low res screens
- Work on performance improvements that will help unblock our ability to ship on more Intel
- Keep on top of important correctness bugs
- Make progress on Android
Correctness
General correctness bugs are currently tracked the following queries. These are not considered blockers for releases and will be re-triaged to assess importance on a regular basis:
- WR-69: https://mzl.la/2Ngn4en
- WR-70: https://mzl.la/2YR4Abk
- WR-71: https://mzl.la/2MiOEHZ
Continued roll-out of WR
One of our main objectives throughout 2019 is to bring WebRender to market on core platforms. For Q3, our main deliverables (in addition to the Android work referenced above) are:
- Identify target for initial WebRender release on Android
- Identify further Android releases/devices to target
WebRender on Desktop
- Ship WebRender to more platforms each release for the remainder of 2019
- Intel Windows 10 with low-res (less than 4K) screens - ride the trains for 69
- Update (08/19) we are moving this target to 70 due to this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1556634
Other
- V1 plan for non-WebRender code path options
- Notes about software backend options: https://github.com/servo/webrender/wiki/Software-backend
- Determine how to measure battery impact of WebRender
The work documented there will help with these specific goals for Q3, as well as our plans throughout the year.
WR on Android
Bugs to fix before enabling WR on GeckoView
August
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
September
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);
Other WR Bugzilla Queries and Info
- Untraiged bugs: https://mzl.la/2CsuGmL
- Blocking Next (bugs blocking next release after MVP): bug 1386674
- Blocking Android bugs: bug 1485449
- Blocking Mac bugs: bug 1479789
- Blocking Linux: bug 1491303
To Do: these lists need to be reviewed to reassessed
Triage info:
Mailing list: dev-tech-gfx@lists.mozilla.org
IRC channel: #gfx
Project owner: Maire Reavy