Title: [250841] trunk/LayoutTests
Revision
250841
Author
grao...@webkit.org
Date
2019-10-08 11:28:51 -0700 (Tue, 08 Oct 2019)

Log Message

fast/events/touch/ios/mouse-events-dispatch-with-touch.html is timing out on iOS
https://bugs.webkit.org/show_bug.cgi?id=202688
<rdar://problem/52700396>

Reviewed by Dean Jackson.

Since this test was originally added, the behavior of simulated mouse events changed to not dispatch any event when there is more than a
single active touch on the screen. This test needs to be adapted to this new behavior.

* fast/events/touch/ios/mouse-events-dispatch-with-touch.html:

Modified Paths

Diff

Modified: trunk/LayoutTests/ChangeLog (250840 => 250841)


--- trunk/LayoutTests/ChangeLog	2019-10-08 18:21:41 UTC (rev 250840)
+++ trunk/LayoutTests/ChangeLog	2019-10-08 18:28:51 UTC (rev 250841)
@@ -1,3 +1,16 @@
+2019-10-08  Antoine Quint  <grao...@apple.com>
+
+        fast/events/touch/ios/mouse-events-dispatch-with-touch.html is timing out on iOS
+        https://bugs.webkit.org/show_bug.cgi?id=202688
+        <rdar://problem/52700396>
+
+        Reviewed by Dean Jackson.
+
+        Since this test was originally added, the behavior of simulated mouse events changed to not dispatch any event when there is more than a
+        single active touch on the screen. This test needs to be adapted to this new behavior.
+
+        * fast/events/touch/ios/mouse-events-dispatch-with-touch.html:
+
 2019-10-08  Youenn Fablet  <you...@apple.com>
 
         Simplify data channel buffer amount low tests

Modified: trunk/LayoutTests/fast/events/touch/ios/mouse-events-dispatch-with-touch.html (250840 => 250841)


--- trunk/LayoutTests/fast/events/touch/ios/mouse-events-dispatch-with-touch.html	2019-10-08 18:21:41 UTC (rev 250840)
+++ trunk/LayoutTests/fast/events/touch/ios/mouse-events-dispatch-with-touch.html	2019-10-08 18:28:51 UTC (rev 250841)
@@ -19,19 +19,21 @@
     const two = ui.finger();
     const three = ui.finger();
     ui.sequence([
-        // Touch "one" will yield mouse events since it's the first touch to begin.
+        // Touch "one" will yield a "mousedown" event since it's the first touch to begin.
         one.begin({ x: 10, y: 10 }),
         // Touch "two" will not yield mouse events since there was already a touch
         // yielding mouse events when it began.
         two.begin({ x: 50, y: 50 }),
         two.move({ x: 70, y: 70 }),
+        // Touch "one" will not yield a "mousemove" since there are currently more than one single active touch.
         one.move({ x: 30, y: 30 }),
+        // Touch "one" will yield a "mouseup" since there is now just one active touch.
         one.end(),
         two.move({ x: 50, y: 50 }),
+        two.end(),
         // Touch "three" will yield mouse events since it's the first touch to begin
         // since the last touch to yield mouse events ("one") ended.
         three.begin({ x: 20, y: 20 }),
-        two.end(),
         three.move({ x: 40, y: 40 }),
         three.end()
     ]).then(() => {
@@ -38,7 +40,6 @@
         eventTracker.assertMatchesEvents([
             // Events dispatched for touch "one".
             { type: "mousedown", x: 10, y: 10 },
-            { type: "mousemove", x: 30, y: 30 },
             { type: "mouseup", x: 30, y: 30 },
             // Events dispatched for touch "three".
             { type: "mousedown", x: 20, y: 20 },
_______________________________________________
webkit-changes mailing list
webkit-changes@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-changes

Reply via email to