Make <webview> use out-of-process iframe architecture.

content/renderer/render_view_impl.cc

Index: content/renderer/render_view_impl.cc
diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc
index eb9971320db4aaff0a97e71a2efcc757be981ee0..2be208403542131f6140cab7575f68c68c83da61 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -739,7 +739,10 @@ void RenderViewImpl::Initialize(const ViewMsg_New_Params& params,
   }
 
   // In --site-per-process, just use the WebRemoteFrame as the main frame.
-  if (command_line.HasSwitch(switches::kSitePerProcess) && proxy) {
+  // Note that we don't do that for guests because postMessage to guest will
+  // break;

[Charlie Reis, 2015/04/30 23:06:47]

nit: Period, not semicolon.  :)

But it also sounds like this might not be necessary, given alexmos's postMessage
work.

[lazyboy, 2015/05/05 07:28:15]

This is reverted as I'm not creating the proxy on RenderView creation anymore,
Since we're now sending a FrameMsg_SwapOut, the proxy is created on that
message's
handler.

+  if (command_line.HasSwitch(switches::kSitePerProcess) &&
+          !params.is_guest && proxy) {
     webview()->setMainFrame(proxy->web_frame());
     // Initialize the WebRemoteFrame with information replicated from the
     // browser process.