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..037b9bc30d3c8576aebe6d0f16660f484274934e 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 apply the cross-site document blocking policy to this

[Charlie Reis, 2013/09/03 22:59:17]

nit: if we should

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

Done.

+  // renderer process. Currently, we apply the policy only to a renderer process
+  // running on a normal page from the web. The cross-site document blocking
+  // policy is not applied to plugin processes too, and it's done in

[Charlie Reis, 2013/09/03 22:59:17]

Better, but I'm still having trouble following the last sentence.  Perhaps:

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.

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

Done.

+  // SiteIsolationPolicy at runtime since requests from a plugin are proxed via
+  // the renderer process that spawned the plugin.
+  virtual bool ShouldEnableSiteIsolationPolicy() const;
 };
 
 }  // namespace content