Always reset touch action at the beginning of a new gesture sequence

content/browser/renderer_host/input/input_router_impl.cc

Index: content/browser/renderer_host/input/input_router_impl.cc
diff --git a/content/browser/renderer_host/input/input_router_impl.cc b/content/browser/renderer_host/input/input_router_impl.cc
index b303acdb94cb21899d3042796cce2fe0c561ca98..6353714586e11f4c4d557d4f2d133e8f6202a11f 100644
--- a/content/browser/renderer_host/input/input_router_impl.cc
+++ b/content/browser/renderer_host/input/input_router_impl.cc
@@ -259,6 +259,8 @@ void InputRouterImpl::SendGestureEvent(
 
 void InputRouterImpl::SendTouchEvent(
     const TouchEventWithLatencyInfo& touch_event) {
+  if (WebInputEventTraits::IsNewTouchSequence(touch_event.event))

[Rick Byers, 2014/02/18 22:01:15]

Doesn't this need to go in SendTouchEventImmediately instead?  If the renderer
is busy and we're queuing up multiple touch sequences in the TEQ, then we may
still be processing gestures associated with the _previous_ sequence.

Can you look into adding a unit test for this sort of timing issue?  I think
it's probably the most subtle/brittle aspect of touch-action behavior.  Perhaps
an input-router unit test with a mock TEQ but real TouchActionFilter?

[tdresser, 2014/02/20 18:37:56]

Done.

+    touch_action_filter_.StartNewTouchActionSequence();
   touch_event_queue_->QueueEvent(touch_event);
 }