-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Call event.stopPropagation() with keyDownEvents specified. #8077
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
Merged
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
NickGerleman
approved these changes
Jun 22, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cc @rozele
2c09a24 to
03542f1
Compare
jonthysell
approved these changes
Jun 22, 2021
| const _keyUp = (event: KeyEvent) => { | ||
| if (props.keyUpEvents && !event.isPropagationStopped) { | ||
| for (const el of props.keyUpEvents) { | ||
| if (event.nativeEvent.code == el.code && el.handledEventPhase == 3) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a constant somewhere we can use (or define) so as to not require a magic number here (and elsewhere)?
packages/@react-native-windows/tester/src/js/examples/Pressable/PressableExample.windows.js
Outdated
Show resolved
Hide resolved
b599e12 to
017845e
Compare
6856878 to
0e5a605
Compare
4 tasks
Saadnajmi
added a commit
to microsoft/react-native-macos
that referenced
this pull request
Oct 9, 2025
…2720) ## Summary: Two changes: - Similar to microsoft/react-native-windows#8077 , we would like to have JS event propagation (as well as native) stop if `keyDownEvents` or `keyUpEvents` is specified. - Add `Space` and `Enter` as default keyDown events for Pressable, to more closely match a button. ## Test Plan: Updated the test page:  --------- Co-authored-by: Tommy Nguyen <4123478+tido64@users.noreply.github.com>
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.
The
key(Down|Up)Eventsprops control whether the event handling should be left exclusively to the JS, or at least the native processing should stop at the native control emitting it. This is to match this behavior on the JS side, by hooking into theonKeyDown|Capturecallback and using event.stopPropagation() on the keys specified inkeyDownEvents.The change is in
Viewand so works forPressabletoo. I've made sure that the existing hooks inPressable, which special-caseSpacecontinue to work with this.Closes #5822
Microsoft Reviewers: Open in CodeFlow