[Webkit-unassigned] [Bug 70836] [chromium] add API methods to support renderer swaps

Fri Nov 18 15:04:40 PST 2011

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

--- Comment #14 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2011-11-18 15:04:40 PST ---
(In reply to comment #12)
> We decided to implement swapping out this way because it lets us get rid of the renderer-side IPC message filtering. If we were to just send back an blank cross-site response, we'd still need to filter out all of the navigation messages the renderer would send.

I see.

> >> Source/WebKit/chromium/public/WebDocument.h:77
> >> +                                            const WebURL&,
> > 
> > By passing a WebURL here, it seems like it is possible for the WebFrame and the WebDocument to have different ideas about what URL is loaded in the frame.  Is that really helpful?  It seems like it could cause subtle bugs.  Another idea would be to infer the URL of the document from the frame.
> 
> Where does the WebFrame keep the current URL? I couldn't find anywhere that it does...

Sorry, it is not so direct.  I was thinking of webFrame->dataSource()->request().url()

I'm curious what it means for us to change the Document without updating the DocumentLoader's state (URL, etc.).

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