[Webkit-unassigned] [Bug 87554] New: Clean up code that has to handle compositing changes on a layer

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 25 17:41:25 PDT 2012


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

           Summary: Clean up code that has to handle compositing changes
                    on a layer
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: simon.fraser at apple.com
                CC: enne at google.com, shawnsingh at chromium.org


We have code in various places that deals with fallout from making a RenderLayer composited, or not. RenderLayerCompositor::updateBacking() has this:

            if (layer->parent())
                layer->computeRepaintRects();
and

    if (layerChanged)
        layer->clearClipRectsIncludingDescendants(PaintingClipRects);

It's not clear if there are all doing the right thing. Why doesn't computeRepaintRects() have to be called for all non-composited descendant layers?

We should have one bottleneck for "my compositing state changed, do stuff to descendants".

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list