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..22d535ec1a4ed7a69e4555bbee206e994483c247 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
+  // renderer process. Currently, we apply the policy only to a render process

[Charlie Reis, 2013/09/03 20:22:10]

render -> renderer
(here and below)

[dsjang, 2013/09/03 22:31:30]

Done.

+  // running on a normal page from the internet, excluding render processes for

[Charlie Reis, 2013/09/03 20:22:10]

internet -> web

[dsjang, 2013/09/03 22:31:30]

Done.

+  // extensions. Unfortunately, there's no easy way to exclude a renderer

[Charlie Reis, 2013/09/03 20:22:10]

nit: Drop "excluding render processes for extensions," since the concept of
extensions doesn't belong in content.

[dsjang, 2013/09/03 22:31:30]

Done.

+  // process for plugins here, but our ultimate goal is to exclude plugin

[Charlie Reis, 2013/09/03 20:22:10]

This last sentence is a bit confusing to me.  We don't create a renderer process
for plugins-- it's sort of the other way around.  Can you rephrase?

[dsjang, 2013/09/03 22:31:30]

Done.

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