611160e516
Previously, picture cache tiles were added to normal batches, and drawn via the brush_image shader. Since all content is now in picture cache tiles, we can instead draw the tiles via a separate code path. The tiles for all picture caches are collected into a single composite config, that is stored in the Frame structure. These two changes provide a number of advantages: * The composite shader is very simple - it doesn't need to deal with transforms, anti-aliasing, repetition etc. * Since we create the tile batches in render(), rather than in the backend, we can take advantage of information not available until the render() call. For example, Gecko will provide information here when the partial presentation rects need to be reset. This will be used to enable partial presentation parameters on Windows. * In future, we can access this list of tiles to be composited, and use them to configure the OS compositor integration, and hand the tiles directly to the OS compositor. * In future, we can apply global optimizations to the set of picture cache tiles (e.g. occlude background tiles on CPU to skip paying the z-reject cost of drawing them). * In future, we can take advantage of the simpler composite path for software rasterizer implementations. Differential Revision: https://phabricator.services.mozilla.com/D47724 --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.