uievents
editWPT coverage of the tests of uievents at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.
| Group | Passing | Tests | Disabled | Pass rate |
|---|---|---|---|---|
| Stable | 64 | 66 | 0 | 97% |
| Tentative | 1 | 3 | 0 | 33% |
| Reftests | 0 | 0 | 0 | – |
| Crash tests | 1 | 1 | 0 | 100% |
| All | 66 | 70 | 0 | 94% |
Failure reasons
The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.
- TEST BUG: 1
- NOT IMPLEMENTED: 2
- REQUIRES: 1
layout: 1
Stable tests
Tentative tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
mouse/mouse_boundary_events_after_reappending_last_over_target.tentative.html | Fail | 3 / 11 | NOT IMPLEMENTED | the boundary events (mouseover, mouseout...) and :hover when the element under an unmoved pointer changes (the hit testing does not run again at the rendering update) |
mouse/offset_and_page_after_dispatch.tentative.html | Pass | 7 / 7 | ||
mouse/synthetic-mouse-enter-leave-over-out-button-state-after-target-removed.tentative.html | Fail | 18 / 22 | NOT IMPLEMENTED | the tentative test expects mouseout and mouseleave at the element a mousedown or mouseup listener removed: the library fires no boundary event at a removed target (the legacy mouse pointer moves to its parent, which gets mouseover), as Pointer Events specifies for the pointer boundary events |
Crash tests
| Test | Result | Variants | Kind | Description |
|---|---|---|---|---|
mouse/crashtests/retrieve_coords_after_moving_target_outside_subdoc_and_hide_the_subdoc.html | Pass | 1 / 1 |