Turn off SiteIsolationPolicy::AreCrossProcessFramesPossible for Android.

content/common/site_isolation_policy.cc

 // Copyright 2015 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.
 
 #include "content/common/site_isolation_policy.h"
 
 #include "base/command_line.h"
 #include "content/public/common/content_switches.h"
 
 namespace content {
 
 // static
 bool SiteIsolationPolicy::AreCrossProcessFramesPossible() {
+// Before turning this on for Android, input event routing needs to be
+// completed there, and perf regressions in https://crbug.com/690229 need to be
+// investigated.
+#if defined(OS_ANDROID)
+  return false;

[nasko, 2017/02/09 21:05:25]

Shouldn't this be the old code that we removed? It should still be conditional
on whether we run in --site-per-process.

[alexmos, 2017/02/09 21:42:31]

Indeed!  Thanks for catching, and I'm glad the bots caught it too.  Fixed now.

+#else
   return true;
+#endif
 }
 
 // static
 bool SiteIsolationPolicy::UseDedicatedProcessesForAllSites() {
   return base::CommandLine::ForCurrentProcess()->HasSwitch(
       switches::kSitePerProcess);
 }
 
 // static
 bool SiteIsolationPolicy::IsTopDocumentIsolationEnabled() {
   // --site-per-process trumps --top-document-isolation.
   if (UseDedicatedProcessesForAllSites())
     return false;
 
   return base::CommandLine::ForCurrentProcess()->HasSwitch(
       switches::kTopDocumentIsolation);
 }
 
 }  // namespace content