NEW 46846
Web Inspector: InspectorController resource tracking needs updating when moving a frame between documents 
https://bugs.webkit.org/show_bug.cgi?id=46846
Summary Web Inspector: InspectorController resource tracking needs updating when movi...
Jenn Braithwaite
Reported 2010-09-29 15:30:52 PDT
When a frame is moved to a new page, the inspector controller of the old page is still tracking the resources for that frame. The resource tracking for those resources needs to be moved to the inspector controller of the new page.
Attachments
Add attachment proposed patch, testcase, etc.
Pavel Feldman
Comment 1 2010-09-30 00:32:04 PDT
Could you please attach an html page / snippet, describe the scenario and existing / expected behavior?
Jenn Braithwaite
Comment 2 2010-09-30 14:08:46 PDT
See the LayoutTests/fast/frames/iframe-reparenting*.html for examples of when a live iframe is reparented using document.adoptNode. These tests move a frame to a new page without interrupting resource loading. The frame tree structure is updated, but resource tracking is not updated. See related bug 44713 dealing with resource tracking in WebViews. This bug deals strictly with updating resource tracking in the inspector controller (separate bug as the fix will be a separate patch). Currently, the frame's former page's inspector controller still tracks the frame's resources after the frame is moved. Expected behavior is that the frame's current page is the one tracking the frame's resources.
Jenn Braithwaite
Comment 3 2010-11-09 10:09:40 PST
Possible places to add hooks to inform the inspector controller of a re-parented frame/resource: WebCore/page/Frame::transferChildFrameToNewDocument() WebCore/loader/FrameLoader::transferLoadingResourcesFromPage()
Radar WebKit Bug Importer
Comment 4 2014-12-17 11:22:12 PST
<rdar://problem/19281500>
Radar WebKit Bug Importer
Comment 5 2014-12-17 11:26:43 PST
<rdar://problem/19281637>
Note You need to log in before you can comment on or make changes to this bug.