-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Create Reconcile keyboarding in desktop proposal doc #5590
Conversation
Adding the doc to the repo for broader review and tracking.
Will this work include TypeScript support for the keyboard props or should I capture that in a separate GH issue? For context we currently have a lot of |
|
|
||
## Default keyboarding behaviors on JS components | ||
|
||
Both Windows and macOS implementations have added appropriate keyboarding defaults to JS components like Button, Touchables. The implementation includes firing onPress() callbacks on Button and Touchable components when they are in focus and Enter/Space key is pressed. The work remaining for these include: |
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.
@harinikmsft @rectified95 Open question about this that comes from an issue of our own implementation right now. PressEvent
exposes bits like pointer coordinates that KeyEvent
s won't have. How do we reconcile these?
Adding the doc to the repo for broader review and tracking.
This addresses the PM design/POR part of #4346
Microsoft Reviewers: Open in CodeFlow