Ensure touch handler state on Android is accurate after preload

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 4f53cd0bf5291fbf61c8648ea3c666ceb0d03ab1..00e2db248cfab1319276a864df673cd2ca97325a 100644
--- a/content/browser/renderer_host/render_widget_host_view_android.cc
+++ b/content/browser/renderer_host/render_widget_host_view_android.cc
@@ -1323,6 +1323,11 @@ void RenderWidgetHostViewAndroid::SetContentViewCore(
     if (content_view_core_ && !using_synchronous_compositor_)
       content_view_core_->GetWindowAndroid()->AddObserver(this);
   }
+
+  // Ensure ContentsViewCore is aware of the current touch handling state, eg.
+  // in case we've already been running JS for the page as part of preload.
+  if (content_view_core_ && host_)
+    content_view_core_->HasTouchEventHandlers(host_->has_touch_handler());

[jdduke (slow), 2014/01/16 22:53:05]

This seems fine.   If we're worried about initialization order, we could always
add some wiring in ContentViewCoreImpl to pull |has_touch_handlers()| from
RWHVA.  That avoids any re-entrance back into ContentViewCore during
initialization.

 }
 
 void RenderWidgetHostViewAndroid::RunAckCallbacks() {