Preserve Page::openedByDOM state across process swaps.

content/browser/renderer_host/render_view_host_impl.h

Index: content/browser/renderer_host/render_view_host_impl.h
diff --git a/content/browser/renderer_host/render_view_host_impl.h b/content/browser/renderer_host/render_view_host_impl.h
index ba6050df268791064c1613f7e9ab16d7cb1dd28d..2922becbc20d109369472575ff279e8342799dc4 100644
--- a/content/browser/renderer_host/render_view_host_impl.h
+++ b/content/browser/renderer_host/render_view_host_impl.h
@@ -248,7 +248,8 @@ class CONTENT_EXPORT RenderViewHostImpl
   // RenderView is told to start issuing page IDs at |max_page_id| + 1.
   virtual bool CreateRenderView(const base::string16& frame_name,
                                 int opener_route_id,
-                                int32 max_page_id);
+                                int32 max_page_id,
+                                bool created_with_opener);

[Charlie Reis, 2014/04/05 01:41:25]

Please document this parameter above.

I agree that this adds some work for us in removing RenderView, but we haven't
starting collecting the cache of page-level state yet in the renderer process. 
(Nasko, were we talking about putting that cached data on the top-level
RenderFrame?  I think some separate PageContext class might be cleaner.)

Anyway, we can add it here for now.

[davidben, 2014/04/07 17:57:52]

Done. I can also do the PageContext thing if those plans are concrete enough
that there's a place to add it that would be useful.

[nasko, 2014/04/08 22:43:25]

I don't think we have clear enough plan for page-level context in the renderer
process. On the browser side, it should be on WebContentsImpl.
It should be fine to add the new param for now, since we aren't close to
removing RenderView and this will be needed even after we remove it.

 
   base::TerminationStatus render_view_termination_status() const {
     return render_view_termination_status_;