2637b20d2f
Previously, the setup_picture_caching function was hard coded to support only a very specific shape of display list. With this change, flags are added to PrimitiveCluster that can specify if a picture cache slice should be created before / after this cluster when picture caching is set up. The usage of these flags in this patch matches the old behaviour, so should not have any functional effect. However, in future we will make use of this functionality to create picture slices for a number of different use cases, such as: * Creating cache tiles for the UI. * Slicing the scene where there are video elements, in order to allow these to be composited directly by the OS. This may also apply to WebGL and/or canvas elements. * Slicing the scene when there is a very large fixed position background image or other element, to avoid invalidating the entire tile cache each frame. Differential Revision: https://phabricator.services.mozilla.com/D46125 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
ci-scripts | ||
debugger | ||
direct-composition | ||
examples | ||
peek-poke | ||
webrender | ||
webrender_api | ||
webrender_build | ||
wr_malloc_size_of | ||
wrench | ||
.gitignore | ||
.taskcluster.yml | ||
appveyor.yml | ||
Cargo.lock | ||
Cargo.toml | ||
LICENSE | ||
README.md | ||
rustfmt.toml | ||
servo-tidy.toml |
WebRender
GPU renderer for the Web content, used by Servo.
Note that the canonical home for this code is in gfx/wr folder of the mozilla-central repository at https://hg.mozilla.org/mozilla-central. The Github repository at https://github.com/servo/webrender should be considered a downstream mirror, although it contains additional metadata (such as Github wiki pages) that do not exist in mozilla-central. Pull requests against the Github repository are still being accepted, although once reviewed, they will be landed on mozilla-central first and then mirrored back. If you are familiar with the mozilla-central contribution workflow, filing bugs in Bugzilla and submitting patches there would be preferred.
Update as a Dependency
After updating shaders in WebRender, go to servo and:
- Go to the servo directory and do ./mach update-cargo -p webrender
- Create a pull request to servo
Use WebRender with Servo
To use a local copy of WebRender with servo, go to your servo build directory and:
- Edit Cargo.toml
- Add at the end of the file:
[patch."https://github.com/servo/webrender"]
"webrender" = { path = "<path>/webrender" }
"webrender_api" = { path = "<path>/webrender_api" }
where <path>
is the path to your local copy of WebRender.
- Build as normal
Documentation
The Wiki has a few pages describing the internals and conventions of WebRender.
Testing
Tests run using OSMesa to get consistent rendering across platforms.
Still there may be differences depending on font libraries on your system, for example.
See this gist for how to make the text tests useful in Fedora, for example.