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

content/browser/renderer_host/input/touch_action_filter.h

Index: content/browser/renderer_host/input/touch_action_filter.h
diff --git a/content/browser/renderer_host/input/touch_action_filter.h b/content/browser/renderer_host/input/touch_action_filter.h
index d4fb4b5550d990fbf715650a01ad032ca3cbc3a6..9e6a666b98bd022ca23de955f27de49061da77d1 100644
--- a/content/browser/renderer_host/input/touch_action_filter.h
+++ b/content/browser/renderer_host/input/touch_action_filter.h
@@ -31,6 +31,8 @@ public:
   // for a touch start event that is currently in flight.
   void OnSetTouchAction(content::TouchAction touch_action);
 
+  void StartNewTouchActionSequence();

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

Add comment please, including mentioning the relative order with other things
(critically - that this is called BEFORE the first touchstart is sent to the
renderer).

I think "TouchActionSequence" doesn't have a well defined meaning.  How about
"OnStartNewTouchSequence"?

Have you thought about the potential for other races here in the context of
eager GR?  I think it's OK, but we should add a comment somewhere explaining why
the start of a new touch sequence is guaranteed to be the start of a new gesture
sequence (maybe even name this function 'OnStartNewGestureSequence' to make it
clear?).

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

Done.

+
   // Return the intersection of two TouchAction values.
   static TouchAction Intersect(TouchAction ta1, TouchAction ta2);