Repository navigation
[0.22] Remove PointerEvent fallback - #2902
Merged
Merged
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 04fab9a:
|
|
Size Change: -1.69 kB (-0.83%) Total Size: 202 kB 📦 View Changed
|
Kudo
approved these changes
Oct 9, 2026
zoontek
force-pushed
the
remove-pointer-events-fallback
branch
from
October 10, 2026 08:53
1bfc2fa to
5109ab4
Compare
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
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.
Important
This PR targets the
0.22-devbranchThe new browser targets all support
PointerEvent, so this PR removes the mouse / touch fallback paths.react-native-web
useHovernow always listens topointerenter,pointermoveandpointerleave, and readse.pointerTypedirectlyuseHoverdrops thex/ypolyfill on hover events (available since Chrome 55)useHoverusesnew CustomEvent()in place ofinitCustomEvent(deprecated)modalitymodule. Its only use was to guess the pointer type whenPointerEventwas not availabledom-event-testing-library
describeWithPointerEvent,hasPointerEventandsetPointerEventtestWithPointerTypealways runs for mouse, touch and penpointerupevent entries, and documentsclearPointers.