Bug 195098 - window.eventSender mouse functions produces different results in WK1 and WK2
Summary: window.eventSender mouse functions produces different results in WK1 and WK2
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-02-27 08:11 PST by Antoine Quint
Modified: 2019-06-04 07:10 PDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Quint 2019-02-27 08:11:55 PST
Three tests added for webkit.org/b/195008 had to be skipped on WK1 because the mouse-related window.eventSender APIs produce different results between WK1 and WK2:

pointerevents/mouse/over-enter-out-leave.html [ Failure ]
pointerevents/mouse/pointer-capture.html [ Failure ]
pointerevents/mouse/pointer-events-before-mouse-events.html [ Failure ]

For instance, the test at pointerevents/mouse/over-enter-out-leave.html starts working if `eventSender.mouseDown()` is called prior to calling any of the other eventSender APIs. This is not required under WK2.
Comment 1 Radar WebKit Bug Importer 2019-02-27 08:12:22 PST
<rdar://problem/48437445>
Comment 2 Antoine Quint 2019-06-04 07:10:01 PDT
The test added for https://bugs.webkit.org/show_bug.cgi?id=198036 also fails for the same reason, pointerevents/mouse/enter-leave-order.html.