Move more of the plugin code in the renderer to use RenderFrame instead of RenderView.

chrome/browser/ui/pdf/pdf_unsupported_feature.cc

Index: chrome/browser/ui/pdf/pdf_unsupported_feature.cc
===================================================================
--- chrome/browser/ui/pdf/pdf_unsupported_feature.cc	(revision 238847)
+++ chrome/browser/ui/pdf/pdf_unsupported_feature.cc	(working copy)
@@ -27,6 +27,7 @@
 #include "content/public/browser/navigation_details.h"
 #include "content/public/browser/navigation_entry.h"
 #include "content/public/browser/plugin_service.h"
+#include "content/public/browser/render_frame_host.h"
 #include "content/public/browser/render_process_host.h"
 #include "content/public/browser/render_view_host.h"
 #include "content/public/browser/user_metrics.h"
@@ -141,9 +142,9 @@
 void OpenUsingReader(WebContents* web_contents,
                      const WebPluginInfo& reader_plugin,
                      OpenPDFInReaderPromptDelegate* delegate) {
-  ChromePluginServiceFilter::GetInstance()->OverridePluginForTab(
+  ChromePluginServiceFilter::GetInstance()->OverridePluginForFrame(
       web_contents->GetRenderProcessHost()->GetID(),
-      web_contents->GetRenderViewHost()->GetRoutingID(),
+      web_contents->GetMainFrame()->GetRoutingID(),

[nasko, 2013/12/05 22:43:45]

Wouldn't this cause overrides to only be stored for the main frame and if a
subframe tries to use unsupported feature, it won't be allowed?
Is this a supported case?

[jam, 2013/12/05 23:14:07]

we only show the page action for top-level pdfs, so it's not an issue

       web_contents->GetURL(),
       reader_plugin);
   web_contents->GetRenderViewHost()->ReloadFrame();