OOPIF: Fix window.open to work from frames with remote parent.

content/browser/renderer_host/render_view_host_delegate.h

Index: content/browser/renderer_host/render_view_host_delegate.h
diff --git a/content/browser/renderer_host/render_view_host_delegate.h b/content/browser/renderer_host/render_view_host_delegate.h
index 21d8a337452bdc35d1e69f9347f5e7e59dd7a398..3554f9944f4d5349a40e88cfcec89409c8119f17 100644
--- a/content/browser/renderer_host/render_view_host_delegate.h
+++ b/content/browser/renderer_host/render_view_host_delegate.h
@@ -195,12 +195,12 @@ class CONTENT_EXPORT RenderViewHostDelegate {
   virtual void LostMouseLock() {}
 
   // The page is trying to open a new page (e.g. a popup window). The window
-  // should be created associated with the given |route_id| in process
-  // |render_process_id|, but it should not be shown yet. That should happen in
-  // response to ShowCreatedWindow.
-  // |params.window_container_type| describes the type of RenderViewHost
-  // container that is requested -- in particular, the window.open call may
-  // have specified 'background' and 'persistent' in the feature string.
+  // should be created associated with the given |route_id| in SiteInstance

[Charlie Reis, 2015/07/09 23:42:51]

nit: in the process of |source_site_instance|,

(Routing IDs are always process specific, so it's worth spelling out that the
process in this case is the one from the SiteInstance.)

[alexmos, 2015/07/10 18:35:00]

Done.

+  // |source_site_instance|, but it should not be shown yet. That should happen
+  // in response to ShowCreatedWindow. |params.window_container_type| describes
+  // the type of RenderViewHost container that is requested -- in particular,
+  // the window.open call may have specified 'background' and 'persistent' in
+  // the feature string.
   //
   // The passed |params.frame_name| parameter is the name parameter that was
   // passed to window.open(), and will be empty if none was passed.
@@ -208,7 +208,7 @@ class CONTENT_EXPORT RenderViewHostDelegate {
   // Note: this is not called "CreateWindow" because that will clash with
   // the Windows function which is actually a #define.
   virtual void CreateNewWindow(

[Charlie Reis, 2015/07/09 23:42:51]

General question: does this belong on RenderFrameHost(Delegate) instead?  It
doesn't seem to be particularly view-specific, and the message is going to come
from a frame.

That could be done in a separate CL, but we could leave a TODO here if it's the
right plan.

[alexmos, 2015/07/10 18:35:00]

Yeah, I agree this should be moved to RenderFrameHostDelegate, and the
corresponding ViewHostMsg_CreateWindow should really be a FrameHostMsg sent to
the creator frame's RFH.  Added a TODO.

-      int render_process_id,
+      SiteInstance* source_site_instance,
       int route_id,
       int main_frame_route_id,
       const ViewHostMsg_CreateWindow_Params& params,