If the canvas is cleared by setting the width or height attributes, its
opaqueness should not be affected.
This patch keeps support for moz-opaque, and also keeps the behavior that
changing the moz-opaque attribute clears the canvas, even if this does not
affect the actual opaqueness of the canvas.
MozReview-Commit-ID: LOlsJxiP9kc
--HG--
extra : rebase_source : 8bb95b1d5932c39a8085e007f9fd1b88b97afe55
- Refactored out Canvas layer mirror specialization, no longer needed
as we are no longer implementing a TextureForwarder to submit VR frames.
MozReview-Commit-ID: ArZO6M9kNLg
--HG--
extra : rebase_source : 2447bfb61b6575f0c6bdaf35ecd4656e7cfb762f
nsICanvasRenderingContextInternal::SetIsOpaque returns nsresult, but no implementations return errors. It should return void instead.
MozReview-Commit-ID: LrGouaeoCvo
--HG--
extra : rebase_source : a17432006aa073edaecf15424a3b350309d704c4
Deprecated ImageBitmapRenderingContext.transferImageBitmap and replaced
it with ImageBitmapRenderingContext.transferFromImageBitmap.
MozReview-Commit-ID: BbNgKrluhT7
--HG--
extra : rebase_source : 2aa3dbfc3acc5d8b1e451111ddbb2cac63f40433
- When a canvas layer is set to mirror, it copies the
texture from the canvas rather than changing the
texture factory with Morph().
- This is useful when a canvas content will be sent to
multiple devices simultaneously, such as a VR HMD
and a 2d monitor mirror.
- This is used by the WebVR 1.0 API, in Bug 1250244
MozReview-Commit-ID: JfMSockO2uz
--HG--
extra : rebase_source : ba9633f7cb9a622efb8389d834b4232205c72755