Remove AreCrossProcessFramesPossible on Android

content/browser/renderer_host/render_widget_host_view_android.cc

Index: content/browser/renderer_host/render_widget_host_view_android.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_android.cc b/content/browser/renderer_host/render_widget_host_view_android.cc
index 975f18cffa05eba56ba0b74206cf2c603516a021..920d7dca7dfd88178d8e992b479cff3010248a5d 100644
--- a/content/browser/renderer_host/render_widget_host_view_android.cc
+++ b/content/browser/renderer_host/render_widget_host_view_android.cc
@@ -1015,9 +1015,15 @@ void RenderWidgetHostViewAndroid::ResetGestureDetection() {
     bool causes_scrolling = false;
     ui::LatencyInfo latency_info(ui::SourceEventType::TOUCH);
     latency_info.AddLatencyNumber(ui::INPUT_EVENT_LATENCY_UI_COMPONENT, 0, 0);
-    host_->ForwardTouchEventWithLatencyInfo(
-        ui::CreateWebTouchEventFromMotionEvent(*cancel_event, causes_scrolling),
-        latency_info);
+    blink::WebTouchEvent web_event =
+        ui::CreateWebTouchEventFromMotionEvent(*cancel_event, causes_scrolling);
+    if (SiteIsolationPolicy::AreCrossProcessFramesPossible() &&

[alexmos, 2017/06/26 17:03:33]

Do we still want to check this, given that it'll always be true now?  (I guess
it'd make sense if this fix were in a separate prerequisite CL, where this being
true wasn't yet guaranteed.)

[kenrb, 2017/06/26 17:25:13]

Done.

+        host_->delegate()->GetInputEventRouter()) {
+      host_->delegate()->GetInputEventRouter()->RouteTouchEvent(
+          this, &web_event, latency_info);
+    } else {
+      host_->ForwardTouchEventWithLatencyInfo(web_event, latency_info);
+    }
   }
 }