Bug 195098
Summary: | window.eventSender mouse functions produces different results in WK1 and WK2 | ||
---|---|---|---|
Product: | WebKit | Reporter: | Antoine Quint <graouts> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | ap, lforschler, simon.fraser, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=195008 https://bugs.webkit.org/show_bug.cgi?id=198036 |
Antoine Quint
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.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/48437445>
Antoine Quint
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.