Decouple RVH creation from CrossProcessFrameConnector.

content/browser/frame_host/cross_process_frame_connector.cc

Index: content/browser/frame_host/cross_process_frame_connector.cc
diff --git a/content/browser/frame_host/cross_process_frame_connector.cc b/content/browser/frame_host/cross_process_frame_connector.cc
index 19fcdf0d4b07713fe2cabee147f26ad574deec00..11894aa699def9d686967d39bef5f4af80dbd4f0 100644
--- a/content/browser/frame_host/cross_process_frame_connector.cc
+++ b/content/browser/frame_host/cross_process_frame_connector.cc
@@ -54,9 +54,11 @@ void CrossProcessFrameConnector::set_view(
 
   view_ = view;
 
-  // Attach ourselves to the new view.
-  if (view_)
+  // Attach ourselves to the new view and size it appropriately.
+  if (view_) {
     view_->set_cross_process_frame_connector(this);
+    OnInitializeChildFrame(child_frame_rect_, device_scale_factor_);

[ncarter (slow), 2014/05/10 00:32:43]

|device_scale_factor_| will be ignored by OnInitializeChildFrame because of its
idempotence check. It doesn't matter in practice, I think, because of how
RenderWidgetHostImpl will look up the screen_info_ on the first WasResized() --
but I think it might be best to avoid this pattern anyhow.

So it might be better to have both OnInitializeChildFrame and this function call
into a shared helper that updates the view based on the values of
child_frame_rect_ and device_scale_factor_ ? Or something like that?

[nasko, 2014/05/16 16:17:30]

Done.

+  }
 }
 
 void CrossProcessFrameConnector::RenderProcessGone() {