[Webkit-unassigned] [Bug 214594] Wrong layer order with negative z-index and will-change: transform

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=214594

--- Comment #3 from Simon Fraser (smfr) <simon.fraser at apple.com> ---
This happens because when we see a negative z-index child, we make its stacking context layer compositing eagerly:

    for (auto* childLayer : layer.negativeZOrderLayers()) {
        computeCompositingRequirements(&layer, *childLayer, overlapMap, currentState, backingSharingState, anyDescendantHas3DTransform);

        // If we have to make a layer for this child, make one now so we can have a contents layer
        // (since we need to ensure that the -ve z-order child renders underneath our contents).
        if (!willBeComposited && currentState.subtreeIsCompositing) {
            layer.setIndirectCompositingReason(IndirectCompositingReason::BackgroundLayer);
            layerWillComposite();
        }
    }

but this messes up the overlap map, so the second negative z-index child doesn't see the rects from the first one.

-- 
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/20200729/2c045fc3/attachment.htm>