Platform/GFX/GFXQ2Goals: Difference between revisions

From MozillaWiki
< Platform‎ | GFX
Jump to navigation Jump to search
Line 43: Line 43:
* Implement position:sticky for Dynamic Toolbar with Webrender (In Progress, ~50% complete)
* Implement position:sticky for Dynamic Toolbar with Webrender (In Progress, ~50% complete)
* Performance report from the performance team (In Progress, ~80% complete)
* Performance report from the performance team (In Progress, ~80% complete)
* Blocking bugs: https://github.com/orgs/FirefoxGraphics/projects/8


======[Not Started] Enable webrender for Mail G7 in nightly======
======[Not Started] Enable webrender for Mail G7 in nightly======

Revision as of 18:49, 2 April 2020

The purpose of this document is to highlight the key projects that the Graphics Team will focus on in Q2 2020.

Objective: Continue WebRender roll out (throughout 2020)

A major goal for the team throughout 2020 is to ship WebRender to as many users as we can.

Ship WebRender throughout Q2 to specific targets for both Desktop and Android

Our detailed plans for WebRender can be found here

Our high-level goals are:

  • Ship WebRender to specific targets per release in Q2
  • Determine critical path for shipping WebRender on older Intel
  • Software WebRender: measure perf as compared to old layers code, identify blockers to shipping and burn down associated tasks

Desktop

Check out www.arewewebrenderyet.com to see where we have enabled WebRender

Goal Progress Blockers/risks
Ship WebRender to specific targets per release in Q2 Targets have been selected, can be viewed here
  • Potential bugs in release could slow us down/cause us to alter plan
Determine critical path for shipping WebRender on older Intel Focused on wr-perf-p1 tasks to help with this
  • Might be additional tasks yet to prioritize
Software WebRender SWGL is in tree, April milestones detailed here
  • Patch has landed that should fix common test failures
  • Next up: look at issue where we are crashing when running tests

A more detailed breakdown of our plans can be found on the WebRender Q2 planning page.

Webrender on Android

Webrender is currently enabled for Adreno 5xx/6xx series on Fenix Nightly. We have not enable Webrender on the Fenix 'release' line.

Upcoming milestones
[In Progress] Enable Webrender on release for a limited set of devices

We currently have no ETA for when we can enable webrender on release due to Fenix release changes. We are working on getting a concrete plan for enabling Webrender on a limited set of devices, most likely Pixel 2 and 2 XL phones.

Dependencies:

  • Improve cold start (no profile/cache) page load by pre-optimizing shaders in build pipeline (In Progress, ~80% complete)
  • Implement position:sticky for Dynamic Toolbar with Webrender (In Progress, ~50% complete)
  • Performance report from the performance team (In Progress, ~80% complete)
  • Blocking bugs: https://github.com/orgs/FirefoxGraphics/projects/8
[Not Started] Enable webrender for Mail G7 in nightly

A substantial amount of bugs are blocking this milestone. Due to efforts on improving load times, this has not been started.

Non-WebRender

  • Fix any important bugs identified during the Fission dogfooding milestone
  • Investigate OffscreenCanvas scope & potential milestones
  • WebGPU

Desktop Zooming

With Kats back working on APZ, we are making good progress and are hoping to enable touchscreen only zooming in next couple of weeks on nightly builds. We are currently evaluating if we can release a touchscreen only MVP before releasing the touchpad implementation.

Upcoming milestones
[In Progress] First nightly release: Windows/Linux Touchscreen Only

Dependency: Hit Testing rework (90% complete)

[In Progress] Mac touchpad

Dependency: Google maps issue (10% complete)

[In Progress] Windows touchpad=

Dependency: Direct Manipulation implementation (50% complete, running into API issues)