[Webkit-unassigned] [Bug 201330] New: On the first compositing update, "drawsContent" can be wrong
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Aug 29 21:40:28 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=201330
Bug ID: 201330
Summary: On the first compositing update, "drawsContent" can be
wrong
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Compositing
Assignee: webkit-unassigned at lists.webkit.org
Reporter: simon.fraser at apple.com
There's an ordering dependency in computing "requiresOwnBackingStore" that causes us to set drawsContent on the GrpahicsLayer when we don't need to, causing test failures:
(bounds 342.00 240.00)
+ (drawsContent 1)
(childrenTransform [1.00 0.00 0.00 0.00] [0.00 1.00 0.00 0.00] [0.00 0.00 1.00 -0.00] [0.00 0.00 0.00 1.00])
The issue is that updateDrawsContent(contentsInfo); happens in RenderLayerBacking::updateAfterDescendants(), but RenderLayerCompositor::requiresOwnBackingStore() on descendants runs before this, and consults compositingAncestorLayer->backing()->graphicsLayer()->drawsContent()
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190830/3b56cd76/attachment.html>
More information about the webkit-unassigned
mailing list