Separate contents_opaque logic on canvas cc::Layer from GraphicsLayer
contents_opaque on the canvas cc::Layer shouldn't depend on its host GraphicsLayer; and the host GraphicsLayer shouldn't use any special logic to determine contents_opaque. This also fixes a CAP-specific bug where the paint code would emit a background DisplayItem for a canvas even when the canvas has responsibility for its own background. As a side effect, this appears to fix a Mac-specific webgl bug that was hidden due to bad test expectations files added by: https://chromium-review.googlesource.com/c/chromium/src/+/1005017/ Bug: 1069546 Change-Id: I2a347a6d4a04d2d8b4e299dd0cb10a3c57acbfb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607423Reviewed-by:Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#840071}
Showing


4.81 KB