Bug 108732 - Sometimes ScrollingTreeFixedNodes are left in the scrolling tree
Summary: Sometimes ScrollingTreeFixedNodes are left in the scrolling tree
Status: RESOLVED DUPLICATE of bug 109348
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Simon Fraser (smfr)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-01 17:46 PST by Simon Fraser (smfr)
Modified: 2013-02-11 13:30 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2013-02-01 17:46:35 PST 
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().
Comment 1 Simon Fraser (smfr) 2013-02-01 18:05:21 PST 
> 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.
Comment 2 Simon Fraser (smfr) 2013-02-11 13:30:52 PST 

*** This bug has been marked as a duplicate of bug 109348 ***