Bug 108732
Summary: | Sometimes ScrollingTreeFixedNodes are left in the scrolling tree | ||
---|---|---|---|
Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
Component: | Layout and Rendering | Assignee: | Simon Fraser (smfr) <simon.fraser> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | bdakin, simon.fraser |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Simon Fraser (smfr)
I've noticed that we can end up with several ScrollingTreeFixedNodes in the scrolling tree even when the page has only one fixedpos element. This happens if the page toggles elements from fixed to non-fixed; e.g. the top bar on http://www.redfin.com/CA/Mountain-View/1075-Space-Park-Way-94043/unit-297/home/21854852
It occurs because RenderLayer::clearBacking() doesn't hit removeViewportConstrainedLayer() when we're destroying the RenderLayer via removeOnlyThisLayer().
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Simon Fraser (smfr)
> It occurs because RenderLayer::clearBacking() doesn't hit removeViewportConstrainedLayer() when we're destroying the RenderLayer via removeOnlyThisLayer().
Actually it does. Something else is happening but I'm not sure what.
Simon Fraser (smfr)
*** This bug has been marked as a duplicate of bug 109348 ***