[Webkit-unassigned] [Bug 99211] New: When ScrollingStateNodes are destroyed, they should be removed ScrollingCoordinator's HashMap

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Oct 12 14:44:10 PDT 2012


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

           Summary: When ScrollingStateNodes are destroyed, they should be
                    removed ScrollingCoordinator's HashMap
           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: bdakin at apple.com


There is a FIXME in ScrollingCoordinatorMac::detachFromStateTree() that says:

    // FIXME: removeNode() will destroy children, and those children might still be in the HashMap.
    // This will be a big problem once there are actually children in the tree.

This bugs is to track resolving that FIXME.

-- 
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