-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure that pointerUp
Action is Being Issued on Element Being Tested
#43214
Conversation
There does not seem to be any guarantee that the pointer will move between actions.
@dshin-moz it looks like this breaks the test in Firefox instead: Did you intend for that to happen? |
Hm.. That's unfortunate - Looking at the logs, the failures happen before the changed line. Checking locally with |
* `pointerMove` origins set on elements instead of viewport + clientRect location * Specifically wait on promise fulfilled microtask being queued after relevant events are emitted * Break down the tests so that one test don't rely on the pointer hovering over where the previous test put it
css/selectors/invalidation/user-action-pseudo-classes-in-has.html
Outdated
Show resolved
Hide resolved
No need to depend on event - Dispatched actions are [guaranteed](https://www.w3.org/TR/webdriver2/#dfn-dispatch-actions-inner) to resolve after DOM events generated by actions are processed.
Keep the test that invalidates from `:has(:hover:active)` -> `:has(:hover)`.
I'm going to admin merge to override the Firefox stability failure. @dshin-moz can you file a Gecko issue for that if it's something you think warrants further investigation? |
There does not seem to be any guarantee that the pointer will move between actions.
Fixes web-platform-tests/interop#606 - verified on local Chromium build.