/pointerevents/mouse-pointer-boundary-events-for-shadowdom.html should allow interleaved pointer and compatibility mouse events

[lilyspiniolas]

Test List

https://wpt.fyi/results/pointerevents/mouse-pointer-boundary-events-for-shadowdom.html?label=experimental&label=master&aligned

Rationale

The test currently checks for an array of four events in a specific order (2 pointer events followed by 2 mouse events) but according to https://w3c.github.io/pointerevents/#compatibility-mapping-with-mouse-events:

At a high level, compatibility mouse events are intended to be "interleaved" with their respective pointer events. However, this specific order is not mandatory, and user agents that implement compatibility mouse events MAY decide to delay or group the dispatch of mouse events, as long as their relative order is consistent.

The test currently fails for the intended (but not required) interleaved order of events, and should be updated to allow for the correct events to occur in any order.

[nt1m]

cc @mustaqahmed @flackr @edgarchen @smaug---- @masayuki-nakano

[mustaqahmed]

Yes the asserts should have allowed interleaving. Thanks for spotting this.

FYI: in pointerevent_support.js, we have the utility method arePointerEventsBeforeCompatMouseEvents() that checks proper interleaving.

[lilyspiniolas]

PR which resolves this issue: https://github.com/web-platform-tests/wpt/pull/47395

[aprotyas]

Closing this issue now that https://github.com/web-platform-tests/wpt/pull/47395 has merged.