Re-enable Eager Gesture Recognition on Aura

content/browser/renderer_host/input/touch_emulator.cc

Index: content/browser/renderer_host/input/touch_emulator.cc
diff --git a/content/browser/renderer_host/input/touch_emulator.cc b/content/browser/renderer_host/input/touch_emulator.cc
index 61ae63ef1fffa283ce8a9e543cefadf9ebc8002b..5b8c9780d9008f490c8086ccabb5e2b81104c08a 100644
--- a/content/browser/renderer_host/input/touch_emulator.cc
+++ b/content/browser/renderer_host/input/touch_emulator.cc
@@ -216,7 +216,7 @@ void TouchEmulator::ForwardTouchEventToClient() {
   const bool event_consumed = true;
   // Block emulated event when emulated native stream is active.
   if (native_stream_active_sequence_count_) {

[jdduke (slow), 2014/12/04 19:27:44]

I wonder if it's worth making these synchronous acks?

[jdduke (slow), 2014/12/04 19:28:16]

By these I mean the two acks within ForwardTouchEventToClient

[tdresser, 2014/12/05 16:44:31]

Done.

-    gesture_provider_.OnTouchEventAck(event_consumed);
+    gesture_provider_.OnAsyncTouchEventAck(event_consumed);
     return;
   }
 
@@ -224,7 +224,7 @@ void TouchEmulator::ForwardTouchEventToClient() {
       WebTouchEventTraits::IsTouchSequenceStart(touch_event_);
   // Do not allow middle-sequence event to pass through, if start was blocked.
   if (!emulated_stream_active_sequence_count_ && !is_sequence_start) {
-    gesture_provider_.OnTouchEventAck(event_consumed);
+    gesture_provider_.OnAsyncTouchEventAck(event_consumed);
     return;
   }
 
@@ -241,7 +241,7 @@ bool TouchEmulator::HandleTouchEventAck(
       emulated_stream_active_sequence_count_--;
 
     const bool event_consumed = ack_result == INPUT_EVENT_ACK_STATE_CONSUMED;
-    gesture_provider_.OnTouchEventAck(event_consumed);
+    gesture_provider_.OnAsyncTouchEventAck(event_consumed);
     return true;
   }