gecko-dev/gfx/wr
Glenn Watson 557728d4ad Bug 1537668 - Refactor how clip task indices are passed to shaders. r=kvark
This patch shouldn't have any functional effect. It's motivated by
some changes needed to implement clip masks in pixel local storage,
but these are also general improvements that stand alone. Specifically:

 - Remove clip_task_index from the global PrimitiveHeader struct.
   In most cases, the clip task is supplied in the BrushInstance
   structure, so it makes no sense to have this as a common field,
   where it is generally unused. Instead, there is now an extra
   'user data' field available in the PrimitiveHeader. Non-brush
   shaders (text_run and split_composite) use that extra field to
   store the clip task address, while the brush shaders gain an extra
   (currently unused) user data field.
 - In turn, this means there is no need to unconditionally try
   and retrieve the first clip task address for a primitive
   during batching. This was previously used to initialize the
   PrimitiveHeader structure.

Differential Revision: https://phabricator.services.mozilla.com/D24312

--HG--
extra : moz-landing-system : lando
2019-03-21 14:37:57 +00:00
..
ci-scripts Bug 1532284 - Build wrench on Android. r=glandium 2019-03-08 00:37:46 +00:00
debugger
direct-composition Bug 1527325 - Don't re-export contents of WR API units r=gw 2019-03-14 01:44:05 +00:00
examples Bug 1527325 - Don't re-export contents of WR API units r=gw 2019-03-14 01:44:05 +00:00
webrender Bug 1537668 - Refactor how clip task indices are passed to shaders. r=kvark 2019-03-21 14:37:57 +00:00
webrender_api Bug 1527325 - Don't re-export contents of WR API units r=gw 2019-03-14 01:44:05 +00:00
webrender_build Bug 1527884 - Make webrender_build publishable. r=kvark 2019-02-19 16:06:01 +00:00
wr_malloc_size_of Bug 1527884 - Make wr_malloc_size_of publishable. r=kvark 2019-02-15 15:47:00 +00:00
wrench Bug 1536732 - Add experimental pixel-local-storage render path to WR r=kvark 2019-03-21 02:59:04 +00:00
.gitignore
.taskcluster.yml Bug 1515348 - Update webrender to commit 75ab41278fe7e24c45b22fa1af6879801d6f8ebc (WR PR #3434). r=kats 2018-12-19 19:28:51 +00:00
appveyor.yml Bug 1514737 - Update webrender to commit 7f2d2ea79e65d49f0da2030e6033761c38c1e296 (WR PR #3408). r=kats 2018-12-17 14:10:46 +00:00
Cargo.lock Bug 1444434 - Bump webrender and webrender_bindings gleam dependency to 0.6.14 r=kvark 2019-03-20 19:52:53 +00:00
Cargo.toml Backed out 2 changesets (bug 1529117) for build bustage 2019-02-27 13:27:50 +02:00
LICENSE
README.md Bug 1507522 - Add a note to the WebRender README about the new upstream. r=kvark 2019-01-10 14:14:00 +00:00
rustfmt.toml
servo-tidy.toml Bug 1510379 - Update webrender to commit 586af96c22c8b05722534e98703bfb47f1d270a1 (WR PR #3338). r=kats 2018-11-27 19:28:45 +00:00

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.