Move RenderViewHost::InsertCSS to RenderFrameHost.

chrome/browser/extensions/extension_view_host.cc

Index: chrome/browser/extensions/extension_view_host.cc
diff --git a/chrome/browser/extensions/extension_view_host.cc b/chrome/browser/extensions/extension_view_host.cc
index e0932d27f84f6bf90fdafb2b14f2a76842e98ce8..a2c38ccb133c45e2ce0d1692473008a9af092953 100644
--- a/chrome/browser/extensions/extension_view_host.cc
+++ b/chrome/browser/extensions/extension_view_host.cc
@@ -14,6 +14,7 @@
 #include "chrome/common/extensions/extension_messages.h"
 #include "components/web_modal/web_contents_modal_dialog_manager.h"
 #include "content/public/browser/notification_source.h"
+#include "content/public/browser/render_frame_host.h"
 #include "content/public/browser/render_view_host.h"
 #include "content/public/browser/web_contents.h"
 #include "content/public/browser/web_contents_view.h"
@@ -333,7 +334,7 @@ void ExtensionViewHost::InsertInfobarCSS() {
       ResourceBundle::GetSharedInstance().GetRawDataResource(
       IDR_EXTENSIONS_INFOBAR_CSS));
 
-  render_view_host()->InsertCSS(base::string16(), css.as_string());
+  host_contents()->GetMainFrame()->InsertCSS(css.as_string());

[jam, 2014/03/06 21:48:48]

we're sure that doing this just for the main frame is fine? please get an
extensions owner to review this

[Avi (use Gerrit), 2014/03/06 21:53:23]

OK. FYI, though, this is exactly what happens today. This changes no behavior.

[jam, 2014/03/06 21:56:29]

ah i missed that, lgtm

 }
 
 }  // namespace extensions