[Gecko Bug 1888013] part 0-1: Port the part.6 of test_bug977003.html to WPT #46275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Differential Revision: https://phabricator.services.mozilla.com/D206206 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1888013 gecko-commit: 4e67f3c5729f204d5c05e2dff3c151467c2a54e1 gecko-reviewers: smaug
Differential Revision: https://phabricator.services.mozilla.com/D206207 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1888013 gecko-commit: 2f7976103a99c4a5bdfb28573c73e534a30862cd gecko-reviewers: smaug
The spec defines that pointer boundary events should be fired before a pointer event if the element under the pointer has been changed from previously dispatching another pointer event. https://w3c.github.io/pointerevents/#dfn-fire-a-pointer-event > Before firing this event, the user agent SHOULD treat the target as if the > pointing device has moved over it from the previousTarget for the purpose of > ensuring event ordering. And releasing pointer capture should be treated as changing an element under the pointer if the pointer is outside the element which lost the capture. Therefore, those tests should expect that `pointerout` should be fired on the capturing element because `pointerover` should be fired on the target. Differential Revision: https://phabricator.services.mozilla.com/D206208 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1888013 gecko-commit: 9276776c01e334df8728dff924ba8d374d8f951a gecko-reviewers: smaug
…re dispatching an `ePointerUp "fire a pointer event" is defined as: https://w3c.github.io/pointerevents/#dfn-fire-a-pointer-event > Before firing this event, the user agent SHOULD treat the target as if the > pointing device has moved over it from the previousTarget for the purpose of > ensuring event ordering. Therefore, `pointerup` should imply a pointer move and cause pointer boundary events before it's dispatched (and after that if non-hoverable pointer, see `pointerup` definition about this). In most cases, it's not required when the input device does not support hover state. However, if the touch target is removed from the tree, the removed element stopped capturing the pointer. In this case, we need to synthesize pointer boundary events before dispatching `pointerup` like inputs from hoverable pointer. Differential Revision: https://phabricator.services.mozilla.com/D206209 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1888013 gecko-commit: 9317687169b17887ad155591bfa2049a70fe418d gecko-reviewers: smaug, edgar, dom-core
wpt-pr-bot
approved these changes
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Differential Revision: https://phabricator.services.mozilla.com/D206206
bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1888013
gecko-commit: 4e67f3c5729f204d5c05e2dff3c151467c2a54e1
gecko-reviewers: smaug