Suppressed MEs for gestures from cancelled PEs

third_party/WebKit/LayoutTests/virtual/pointerevent/fast/events/pointerevents/touch-pointer-mouse-expected.txt

Index: third_party/WebKit/LayoutTests/virtual/pointerevent/fast/events/pointerevents/touch-pointer-mouse-expected.txt
diff --git a/third_party/WebKit/LayoutTests/virtual/pointerevent/fast/events/pointerevents/touch-pointer-mouse-expected.txt b/third_party/WebKit/LayoutTests/virtual/pointerevent/fast/events/pointerevents/touch-pointer-mouse-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..9fa4b1b1f6f2e6e56454f52956868114c85be6db
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/virtual/pointerevent/fast/events/pointerevents/touch-pointer-mouse-expected.txt
@@ -0,0 +1,61 @@
+Verifies that canceling pointerdowns for touches correctly suppresses mouseevents.
+
+On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
+
+
+=== With primary pointerdown uncanceled ===
+-- Quick tap --
+Received pointerdown primary
+Received touchstart 
+Received pointerup primary
+Received touchend 
+Received mousemove 
+Received mousedown 
+Received mouseup 
+Received click 
+-- Long tap --
+Received pointerdown primary
+Received touchstart 
+Received mousemove 
+Received pointerdown primary
+Received mousedown 
+Received pointerup primary
+Received touchend 
+
+=== With primary pointerdown canceled ===
+-- Quick tap --
+Received pointerdown primary,canceled
+Received touchstart 
+Received pointerup primary
+Received touchend 
+Received click 
+-- Long tap --
+Received pointerdown primary,canceled
+Received touchstart 
+Received mousemove 

[Rick Byers, 2016/05/27 20:39:27]

Your CL description says that you're still firing mousedown on GestureLongPress,
but I don't see it here...

[mustaq, 2016/05/30 15:14:26]

Yes, I noticed it too, that's why I added the long-press tests in this CL: the
mousedown is gone from here as well as from the next block of test where the
primary pointerdown not even canceled. I will debug it today.

[mustaq, 2016/06/02 19:26:26]

The way I was sending TE+GE sequence for long-tap thorough eventSender doesn't
match the reality in some way, causing some inconsistent state in EventSender.
Chrome behaves perfectly when I mimic the tap+LongTap sequence manually. I will
figure out the correct TE+GE firing sequence in my followup (LongPress) CL.

+Received pointerdown primary,canceled
+Received pointerup primary
+Received touchend 
+
+=== With primary pointerdown uncanceled ===
+-- Quick tap --
+Received pointerdown primary
+Received touchstart 
+Received pointerup primary
+Received touchend 
+Received mousemove 
+Received mousedown 
+Received mouseup 
+Received click 
+-- Long tap --
+Received pointerdown primary
+Received touchstart 
+Received mousemove 
+Received pointerdown primary
+Received pointerup primary
+Received touchend 
+
+PASS successfullyParsed is true
+
+TEST COMPLETE
+