[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..7bb6c5d331d828cf94b5900a2c1a63eace3b39e2 100644
--- a/chrome/renderer/chrome_content_renderer_client.cc
+++ b/chrome/renderer/chrome_content_renderer_client.cc
@@ -1538,12 +1538,11 @@ 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; we would need to

[Lei Zhang, 2015/06/16 22:41:20]

If there's a bug # associated with this, please include it.

[ncarter (slow), 2015/06/16 23:00:18]

Done.

+  // check the extension's manifest to know which sites it's allowed to access.
 #if defined(ENABLE_EXTENSIONS)
   base::CommandLine* command_line = base::CommandLine::ForCurrentProcess();
   return !command_line->HasSwitch(extensions::switches::kExtensionProcess);