Disable CrossSiteDocumentBlockingForDifferentTargets for --site-per-process.

content/child/site_isolation_policy_browsertest.cc

Index: content/child/site_isolation_policy_browsertest.cc
diff --git a/content/child/site_isolation_policy_browsertest.cc b/content/child/site_isolation_policy_browsertest.cc
index c23b9b98759c1b79b6117e73ee3558458b8da3cc..d4ad79d8a3ed6549e903f1dc40c1b2db5006cb71 100644
--- a/content/child/site_isolation_policy_browsertest.cc
+++ b/content/child/site_isolation_policy_browsertest.cc
@@ -93,6 +93,13 @@ IN_PROC_BROWSER_TEST_F(SiteIsolationPolicyBrowserTest,
 
 IN_PROC_BROWSER_TEST_F(SiteIsolationPolicyBrowserTest,
                        MAYBE_CrossSiteDocumentBlockingForDifferentTargets) {
+  // TODO(creis): Re-enable this test in --site-per-process mode once we support
+  // sibling frames from the same site with correct DidStopLoading behavior.
+  // See http://crbug.com/419087 and http://crbug.com/436250.
+  if (base::CommandLine::ForCurrentProcess()->HasSwitch(
+          switches::kSitePerProcess))
+    return;
+
   // This webpage loads a cross-site HTML page in different targets such as
   // <img>,<link>,<embed>, etc. Since the requested document is blocked, and one
   // character string (' ') is returned instead, this tests that the renderer