Don't pass touches to gesture recognizer for async acks.

content/browser/renderer_host/render_widget_host_view_aura.cc

Index: content/browser/renderer_host/render_widget_host_view_aura.cc
diff --git a/content/browser/renderer_host/render_widget_host_view_aura.cc b/content/browser/renderer_host/render_widget_host_view_aura.cc
index 49ee8e48f09e47f0b9305899e12443c993a9e26f..cdb7df4f2de135a9ffbeb23316cccea61ca0d63a 100644
--- a/content/browser/renderer_host/render_widget_host_view_aura.cc
+++ b/content/browser/renderer_host/render_widget_host_view_aura.cc
@@ -1140,11 +1140,6 @@ void RenderWidgetHostViewAura::GestureEventAck(
 
 void RenderWidgetHostViewAura::ProcessAckedTouchEvent(
     const TouchEventWithLatencyInfo& touch, InputEventAckState ack_result) {
-  ScopedVector<ui::TouchEvent> events;
-  if (!MakeUITouchEventsFromWebTouchEvents(touch, &events,
-                                           SCREEN_COORDINATES))
-    return;
-
   aura::WindowTreeHost* host = window_->GetHost();
   // |host| is NULL during tests.
   if (!host)
@@ -1152,10 +1147,8 @@ void RenderWidgetHostViewAura::ProcessAckedTouchEvent(
 
   ui::EventResult result = (ack_result ==
       INPUT_EVENT_ACK_STATE_CONSUMED) ? ui::ER_HANDLED : ui::ER_UNHANDLED;
-  for (ScopedVector<ui::TouchEvent>::iterator iter = events.begin(),
-      end = events.end(); iter != end; ++iter) {
-    host->dispatcher()->ProcessedTouchEvent((*iter), window_, result);
-  }
+  for (size_t i = 0; i < touch.event.touchesLength; ++i)
+    host->dispatcher()->ProcessedTouchEvent(window_, result);

[sadrul, 2014/08/26 20:09:07]

With this change, we are going to be ack-ing more times than we do currently.
For example, if there are multiple active touch-points, and we sent an update
for a single touch-point, then upon the ACK, we would call ProcessedTouchEvent()
just once. With this change, we would call this for each touch-point (including
the stationary ones). Would that not cause issues?

[tdresser, 2014/08/27 17:40:24]

Easy fix, hard test...

https://code.google.com/p/chromium/codesearch#chromium/src/ui/events/gesture_...
makes this fail silently.

I suppose I could disable that early out for a browsertest, and test it that
way... Any other ideas?

 }
 
 scoped_ptr<SyntheticGestureTarget>