[Webkit-unassigned] [Bug 48356] New: Need API to stop tracking a resource after it has been moved to a different document

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 26 11:42:10 PDT 2010


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

           Summary: Need API to stop tracking a resource after it has been
                    moved to a different document
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jennb at chromium.org
                CC: ap at webkit.org, dimich at chromium.org


When a live iframe is moved to a different document (via adoptNode), tracking of its resources is also moved to the new document.  Currently, resource tracking continues until the load finishes or fails.  There is no API to tell a client to stop tracking a resource that is still loading.  This leaves the former document's FrameLoaderClient tracking a resource that it no longer owns, and for which it will never receive any further notifications.  This may also create a conflict if the frame eventually gets adopted back into its original document.

See bug 44713 for more background context.  It was recommended that I file a WebKit2 bug instead of adding new Mac API in the patch for that fix.

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