[Webkit-unassigned] [Bug 70836] New: [chromium] add swapOut method to WebFrame

[bugzilla-daemon at webkit.org]

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

           Summary: [chromium] add swapOut method to WebFrame
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://crbug.com/101393
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: supersat at chromium.org
                CC: fishd at chromium.org, creis at chromium.org,
                    mihaip at chromium.org


Chromium now "swaps out" the current renderer on a cross-site request instead of destroying it. This allows the renderer to be swapped back in if the user navigates back to the original site, preserving window.opener (which would be null if we just did another process swap -- see http://crbug.com/65953). To perform a swap out, we need to unload the current document in the renderer to prevent any scripts or plugins from continuing to execute. Currently, this is done with a hack where the renderer is navigated to about:swappedout and spurious IPC messages generated by this navigation are filtered out. However, a cleaner way of swapping out a renderer is to just unload the current document, but no WebKit API exists for doing so. Adding a swapOut method to Chromium's WebFrame that would unload the current document would allow us to simplify the swap out code.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.