Suppressed MEs for gestures from cancelled PEs

third_party/WebKit/public/web/WebInputEvent.h

Index: third_party/WebKit/public/web/WebInputEvent.h
diff --git a/third_party/WebKit/public/web/WebInputEvent.h b/third_party/WebKit/public/web/WebInputEvent.h
index 08ef45c6f02c0af656fdce96f309b574c5ee4a60..f18cc5bead4febd6e08549346e887954fb2aebd6 100644
--- a/third_party/WebKit/public/web/WebInputEvent.h
+++ b/third_party/WebKit/public/web/WebInputEvent.h
@@ -495,6 +495,12 @@ public:
     int globalX;
     int globalY;
     WebGestureDevice sourceDevice;
+
+    // If the WebGestureEvent has sourceDevice=WebGestureDeviceTouchscreen, this
+    // field contains the unique identifier for the touch event that triggered

[Rick Byers, 2016/06/03 15:31:40]

please define a bit more precisely WHICH touch event this corresponds to
("triggers" is pretty vague).  Eg. for a GestureScrollUpdate is it the
touchmove?  What about for a GestureLongPress?  Is it "the ID of the most recent
event which, if cancelled, would have suppressed the generation of this gesture
event"?

This might get a little hairy in the general case.  You could perhaps avoid the
confusion/complexity by saying it represents the entire sequence (not a specific
event) and does so by referring to the event ID for the touchstart of the first
finger involved in the gesture.  This might be more work to implement on the
content side though.

[mustaq, 2016/06/03 20:34:45]

Does the comment sound better now? This is set on releasing the GE from TDGF, so
"trigger" wasn't the right word.

+    // the gesture. Otherwise, it contains 0.
+    uint32_t uniqueTouchEventId;
+
     // This field exists to allow BrowserPlugin to mark GestureScroll events as
     // 'resent' to handle the case where an event is not consumed when first
     // encountered; it should be handled differently by the plugin when it is