Confirm
156
edits
Changes
Add mozilla-central contribution workflow
<b>Note:</b> WebRender may still be disabled by other runtime conditions. Common conditions include a disabled GPU process (on Windows) or disabled hardware acceleration. You can check the WebRender status by going to about:support and looking at the WebRender line in the graphics section. On Linux hardware acceleration is disabled by default, so set <tt>layers.acceleration.force-enabled</tt> to true in about:config (restart required), or run with <tt>MOZ_ACCELERATED=1</tt> in the environment to ensure HWA is enabled and doesn't block WebRender.
=== Contribution workflow ===
You can hack on WebRender either via a checkout of mozilla-central or via a checkout of the webrender repository. Using mozilla-central allows you to easily build/test Firefox and trigger try pushes, especially when you have interdependent changes across Firefox and WebRender. You can also build standalone WebRender from within mozilla-central, via i.e.
cd gfx/webrender
cargo build --features=capture,replay,pathfinder
If you use mozilla-central, you have the option to request review via Phabricator, but your final changes must not land directly, and should be submitted to the standalone WebRender repository. Git users can do this like so:
cd /path/to/m-c
git format-patch -pk --relative=gfx BASE_REVISION gfx/webrender gfx/webrender_api
cd /path/to/webrender
git checkout -b my_branch
git am /path/to/m-c/0*
git push my_branch
You should then ping a bors operator to carry your apply your r+ to the GitHub PR. Once your change lands in upstream WebRender, it will be synced to mozilla-central within a day or two.
=== Testing third-party rust library changes ===
