Pass WebKit priority changes and parsing messages up to the browser process.

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 e15789b83bebe2dd3d37bff0fc2e20f58b640f08..06923e885d821968c084f5cdc109219990126d71 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -4475,6 +4475,12 @@ void RenderViewImpl::didLoseWebGLContext(
       arb_robustness_status_code));
 }
 
+void RenderViewImpl::willInsertBody(WebKit::WebFrame* frame) {
+  if (frame == webview()->mainFrame()) {

[darin (slow to review), 2013/02/07 07:40:41]

nit: !frame->parent() is a slightly more compact way of checking for topmost

[James Simonsen, 2013/02/11 22:53:11]

Done.

+    Send(new ViewHostMsg_DidParseBody(routing_id()));

[darin (slow to review), 2013/02/07 07:40:41]

Maybe the IPC message should also use the term "Insert" instead of "Parse"?  Or,
is willInsertBody misnamed?

[James Simonsen, 2013/02/11 22:53:11]

Done.

Either name is accurate. There's a delay between when the body is parsed and
when it's inserted, because it's a micro-task that does it. I've made it
consistently WillInsertBody throughout.

+  }
+}
+
 // WebKit::WebPageSerializerClient implementation ------------------------------
 
 void RenderViewImpl::didSerializeDataForFrame(