Platform/GFX/WebRender2020 Q3

WebRender Q3 2020

The purpose of this document is to highlight our priorities for WebRender in Q2 of 2020

Where have we shipped WebRender?

For a list of the various places we have shipped WebRender, see: https://wiki.mozilla.org/Platform/GFX/WebRender_Where

We are also currently working on a WebRender dashboard, this is very much a WIP

Core Priorities

Shipping WebRender

We want to keep shipping WebRender to as many targets as possible each quarter.

Q2 will be the quarter where we start shipping WebRender on more Intel laptops (Win10). This is a critical next phase of the project as this represents a significant portion of the desktop population.

It is important to note: we expect to encounter fallout bugs in release once we start shipping to more Intel. So our plan for Q2 includes holding off shipping to new platforms for at least one target while we focus on bug fixing. If that turns out to not be necessary, we will adjust plans as necessary.

Windows10 will also remain as our priority platform for the quarter, and we will start assessing additional platforms pending our overall progress.

Below is a list of releases in Q2 and what we are aiming to ship per release:

75 (April 7)

• Desktop
  • Direct Composition (needed to unblock more Intel laptops)
    • Specifically to Win10 and newer Intel Graphics cards

76 (May 5)

• Desktop
  • Intel Laptops
    • Single modern Intel GPU's, small screens, with batteries and modern drivers and Win10 (latest build)
    • https://bugzilla.mozilla.org/show_bug.cgi?id=1615049

• Android
  • WebRender will be enabled in Fenix 'release' when it ships 4.4
    • Pixel 2/3 https://bugzilla.mozilla.org/show_bug.cgi?id=1607322

77 (June 2)

• More Nvidia laptops: https://bugzilla.mozilla.org/show_bug.cgi?id=1628809
  • If we have too many fallout bugs from 76, we may postpone this

78 (June 30)

• Desktop
  • Laptops and Desktop with medium and large screens and modern Intel GPUs

• Android
  • Further targets TBD based on overall Android planning

As part of this effort, we will need to monitor and fix any critical correctness or perf bugs that appear that could potentially block shipping those targets or could impact users in release.