1f61ebcbc9
The `opaque_rect` in `SurfaceInfo` is used to determine whether a picture with a backing surface can be considered opaque during batching, to select an appropriate blend mode. Instead of checking every primitive during the prepare pass, take advantage of the backdrop candidate detection done by picture caching during the visibility pass to find opaque pictures. Strictly speaking, this doesn't catch quite as many cases as the previous code, because it doesn't try to union rects and it doesn't check every single primitive. However, it catches the vast majority of real world cases, where there is a single background primitive that covers the picture surface (e.g. color, gradient, image etc). Any future improvements to the picture backdrop logic will also automatically apply to the new picture opaque detection logic. The primary benefits are improved performance, by removing some per-primitive work that was being done during the prepare pass, and removing another field from `PrimitiveCluster` which will be changing signficantly in future. Differential Revision: https://phabricator.services.mozilla.com/D132000 |
||
---|---|---|
.. | ||
ci-scripts | ||
example-compositor | ||
examples | ||
glsl-to-cxx | ||
peek-poke | ||
swgl | ||
webrender | ||
webrender_api | ||
webrender_build | ||
wr_malloc_size_of | ||
wrench | ||
.gitignore | ||
.taskcluster.yml | ||
Cargo.lock | ||
Cargo.toml | ||
LICENSE | ||
README.md | ||
rustfmt.toml | ||
servo-tidy.toml |
README.md
WebRender
WebRender is a GPU-based 2D rendering engine written in Rust. Firefox, the research web browser Servo, and other GUI frameworks draw with it. It currently uses the OpenGL API internally.
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.