Instead of waiting until the WebRenderLayerManager destructor runs, we can
send the destroy message a little earlier, when it is Destroy()'d. Also add
a guard to prevent double-destruction, just in case.
MozReview-Commit-ID: 8pCRwH7Xecw
Revert "Bug 1318066 - Provide WR with the path to the resources directory. r=jrmuizel?"
This reverts commit 6aeb295d19b80c368cb3a31a096ac76b745797df
Revert "Bug 1318066 - Ensure webrender resources are bundled into the Firefox installation. r=jrmuizel?"
This reverts commit fdfd418626ad2bedc33a6bd813a3472617a9b1e3
MozReview-Commit-ID: FXSAXK5qsmr
The overall architecture here is that we add a new layers type, LAYERS_WR,
which can be used in place of client layers. The WebRenderLayerManager, in
the EndTransaction call, paints content into images and ships them over the
PWebRenderBridge to the compositor thread. The WebRenderBridgeParent code on
the compositor side talks to WebRender via the API in webrender.h.
MozReview-Commit-ID: JKLTLJWVXiN
