Tie extension/app initialization to RenderView creation, not RenderViewHost creation

content/browser/renderer_host/render_view_host.cc

Index: content/browser/renderer_host/render_view_host.cc
diff --git a/content/browser/renderer_host/render_view_host.cc b/content/browser/renderer_host/render_view_host.cc
index 3d360a2f7f4461e675b68d79e3f8477f1ae59eb3..05f11b4eea6562aa7261d68f0ad758eba93eea57 100644
--- a/content/browser/renderer_host/render_view_host.cc
+++ b/content/browser/renderer_host/render_view_host.cc
@@ -192,6 +192,7 @@ bool RenderViewHost::CreateRenderView(const string16& frame_name) {
   Send(new ViewMsg_AllowBindings(routing_id(), enabled_bindings_));
   // Let our delegate know that we created a RenderView.
   delegate_->RenderViewCreated(this);
+  content::GetContentClient()->browser()->RenderViewCreated(this);

[jam, 2011/08/11 18:13:37]

It's best to avoid adding methods to ContentBrowserClient unless there's no
other way (i.e. at the point that content needs to tell the embedder, there's no
other context). The reason is that ContentBrowserClient is already pretty large,
and the smaller we can keep it the easier it'll be for embedders.

In this case, we already tell the RenderViewHostObservers. Chrome implements one
in chrome/browser/renderer_host/chrome_render_view_host_observer.cc, so how
about moving the code there?

 
   FOR_EACH_OBSERVER(
       RenderViewHostObserver, observers_, RenderViewHostInitialized());