NEW48356
Need API to stop tracking a resource after it has been moved to a different document 
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 d...
Jenn Braithwaite
Reported 2010-10-26 11:42:10 PDT
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.
Attachments
Add attachment proposed patch, testcase, etc.
Note You need to log in before you can comment on or make changes to this bug.