d6bac95db7
Previously, picture caching code would use the viewport of the scroll root to find a clipping rect for picture cache tiles. This viewport rect was also used to eliminate fixed position clip rects on primitives that would otherwise cause unwanted invalidations due to them moving relative to the scroll root when scrolls occur. Now, the picture caching code uses a similar technique to Gecko to find shared clips on primitives in a picture cache. These clips are filtered out from being applied on a per-primitive basis, and instead applied once during compositing the tiles into the parent picture. This is a potential performance improvement, since less per-item work is required when building clip chains. More importantly, it means the picture caching code correctly handles cases where the scroll root contains fixed position elements (or other scroll roots). This is a requirement before we can enable picture caching on multiple slices. Differential Revision: https://phabricator.services.mozilla.com/D44618 --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 | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
| appveyor.yml | ||
| rustfmt.toml | ||
| servo-tidy.toml | ||
README.md
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.