Ensure touch handler state on Android is accurate after preload

content/browser/renderer_host/render_widget_host_view_android.cc

 // Copyright (c) 2012 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/browser/renderer_host/render_widget_host_view_android.h"
 
 #include <android/bitmap.h>
 
 #include "base/basictypes.h"
 #include "base/bind.h"
@@ skipping 1305 matching lines @@
       obj = content_view_core_->GetJavaObject();
     GetBrowserAccessibilityManager()->ToBrowserAccessibilityManagerAndroid()->
         SetContentViewCore(obj);
   }
 
   if (are_layers_attached_) {
     AttachLayers();
     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() {
   while (!ack_callbacks_.empty()) {
     ack_callbacks_.front().Run();
     ack_callbacks_.pop();
   }
 }
 
 void RenderWidgetHostViewAndroid::HasTouchEventHandlers(
@@ skipping 116 matching lines @@
 // RenderWidgetHostView, public:
 
 // static
 RenderWidgetHostView*
 RenderWidgetHostView::CreateViewForWidget(RenderWidgetHost* widget) {
   RenderWidgetHostImpl* rwhi = RenderWidgetHostImpl::From(widget);
   return new RenderWidgetHostViewAndroid(rwhi, NULL);
 }
 
 } // namespace content