Whitelisting exts and plugins from cross-site document blocking

content/public/renderer/content_renderer_client.h

Index: content/public/renderer/content_renderer_client.h
diff --git a/content/public/renderer/content_renderer_client.h b/content/public/renderer/content_renderer_client.h
index 4eea8a3c12830d31f4dc1f0ff8c75a715c8e34ef..4d06c0f3a8b2756122a3db8d560ff1a41defeb93 100644
--- a/content/public/renderer/content_renderer_client.h
+++ b/content/public/renderer/content_renderer_client.h
@@ -250,6 +250,14 @@ class CONTENT_EXPORT ContentRendererClient {
   // and can be external or internal.
   virtual bool ShouldReportDetailedMessageForSource(
       const base::string16& source) const;
+
+  // Returns true if we should apply the cross-site document blocking policy to
+  // this renderer process. Currently, we apply the policy only to a renderer
+  // process running on a normal page from the web. The policy should not be
+  // applied to plugin processes, which currently proxy their network requests
+  // through renderer processes.  As a result, SiteIsolationPolicy checks for
+  // plugin requests in renderer processes at runtime and ignores them.

[jam, 2013/09/04 00:32:24]

nit: it's a bit odd that this comment talks about plugins, when this callback
has nothing to do with plugins. so i would take that part out.

[dsjang, 2013/09/04 00:37:37]

Done.

+  virtual bool ShouldEnableSiteIsolationPolicy() const;
 };
 
 }  // namespace content