Experimental: Fix HasWrongProcessForURL in --site-per-process mode.

chrome/browser/chrome_content_browser_client.cc

Index: chrome/browser/chrome_content_browser_client.cc
diff --git a/chrome/browser/chrome_content_browser_client.cc b/chrome/browser/chrome_content_browser_client.cc
index 4a83631379cb3f1b3e04ee220030ea9f36837e49..49fa60a17cc30cd3287e56cf218972845b1d1fa6 100644
--- a/chrome/browser/chrome_content_browser_client.cc
+++ b/chrome/browser/chrome_content_browser_client.cc
@@ -712,18 +712,6 @@ bool ChromeContentBrowserClient::IsSuitableHost(
   if (!service || !process_map)
     return true;
 
-  // Experimental:
-  // If --enable-strict-site-isolation or --site-per-process is enabled, do not
-  // allow non-WebUI pages to share a renderer process.  (We could allow pages
-  // from the same site or extensions of the same type to share, if we knew what
-  // the given process was dedicated to.  Allowing no sharing is simpler for
-  // now.)  This may cause resource exhaustion issues if too many sites are open
-  // at once.
-  const CommandLine& command_line = *CommandLine::ForCurrentProcess();
-  if (command_line.HasSwitch(switches::kEnableStrictSiteIsolation) ||
-      command_line.HasSwitch(switches::kSitePerProcess))
-    return false;
-
   // Otherwise, just make sure the process privilege matches the privilege
   // required by the site.
   RenderProcessHostPrivilege privilege_required =