Fix touch events on Android mobile (Fenix) #472
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #440
Firefox for Android (Fenix) does not implement the recommendation for non-hover pointer events, but does implement the requirements. Ie, a
pointeroverevent will be fired just beforepointerdown, but nothing more.This is in contrast to Firefox on desktop or Chrome (even on Android), which will also fire
mousemove/pointermoveevents as the spec recommends.Since this is technically valid behavior, and events are not sent downstream until a move is received, this PR adds handling for the pointerover event similar to a move in regards to the internal pointer state.