Whitelisting exts and plugins from cross-site document blocking

content/public/renderer/content_renderer_client.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CONTENT_PUBLIC_RENDERER_CONTENT_RENDERER_CLIENT_H_
 #define CONTENT_PUBLIC_RENDERER_CONTENT_RENDERER_CLIENT_H_
 
 #include <string>
 
 #include "base/memory/weak_ptr.h"
@@ skipping 232 matching lines @@
 
   // Returns true if the page at |url| can use Pepper MediaStream APIs.
   virtual bool AllowPepperMediaStreamAPI(const GURL& url);
 
   // Returns true if we should report a detailed message (including a stack
   // trace) for console [logs|errors|exceptions]. |source| is the WebKit-
   // reported source for the error; this can point to a page or a script,
   // 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
 
 #endif  // CONTENT_PUBLIC_RENDERER_CONTENT_RENDERER_CLIENT_H_