[Patch 3 of 6] Split out content/child's SiteIsolationPolicy into two new classes.

chrome/renderer/chrome_content_renderer_client.cc

Index: chrome/renderer/chrome_content_renderer_client.cc
diff --git a/chrome/renderer/chrome_content_renderer_client.cc b/chrome/renderer/chrome_content_renderer_client.cc
index 59de107ca5069b00d9b84ab1490be9064a249b03..5aaa6ba0b34fa535a6bb174fce0f7fec533894fb 100644
--- a/chrome/renderer/chrome_content_renderer_client.cc
+++ b/chrome/renderer/chrome_content_renderer_client.cc
@@ -1538,12 +1538,10 @@ bool ChromeContentRendererClient::ShouldReportDetailedMessageForSource(
 #endif
 }
 
-bool ChromeContentRendererClient::ShouldEnableSiteIsolationPolicy() const {
-  // SiteIsolationPolicy is off by default. We would like to activate cross-site
-  // document blocking (for UMA data collection) for normal renderer processes
-  // running a normal web page from the Internet. We only turn on
-  // SiteIsolationPolicy for a renderer process that does not have the extension
-  // flag on.
+bool ChromeContentRendererClient::ShouldGatherSiteIsolationStats() const {
+  // Site isolation stats are gathered currently for non-extension renderer
+  // processes running a normal web page from the Internet.
+  // TODO(nick): Gather stats for extension processes too.

[Charlie Reis, 2015/06/16 21:21:51]

Let's mention what's blocking this, since I forgot again.  :)  It's because we
would need to check the extension's manifest to know which sites it's allowed to
make XHRs to, I think.

[ncarter (slow), 2015/06/16 22:24:48]

Done.

 #if defined(ENABLE_EXTENSIONS)
   base::CommandLine* command_line = base::CommandLine::ForCurrentProcess();
   return !command_line->HasSwitch(extensions::switches::kExtensionProcess);