forked from facebook/react-native
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Deprecate acceptsKeyboardFocus #498
Labels
Comments
Updating the original description, since the RNW deprecation ended up happening in 0.63. The version matrix basically looked like:
The TLDR: react-native-macos will need to add focusable by 0.63, and will be able to fully remove acceptsKeyboardFocus in 0.64. Deprecation warnings at runtime are useful since folks are using acceptsKeyboardFocus without typings. |
NickGerleman
added a commit
to NickGerleman/react-native
that referenced
this issue
Nov 18, 2020
Fixes microsoft#498 This change adds support for the "focusable" property present in upstream RN, along with react-native-windows and NetUI. We need to reconcile this against the existing acceptsKeyboardFocus property. This is tricky since its usage was untyped. We follow the same strategy as react-native-windows for this. 1. Usages of acceptsKeyboardFocus will continue to work, but will yellowbox 2. Components will prefer to use focusable, and Touchables with slightly different semantics will prefer focusable semantics when present acceptsKeyboardFocus will redbox in RNW 0.64 instead of yellowbox, but this change should allow xplat code to use focusable and not be effected by that. Validated setting a view to focusable is propagated, and that acceptsKeyboardFocus is propagated with a yellowbox.
4 tasks
NickGerleman
added a commit
that referenced
this issue
Nov 19, 2020
* Support focusable, Yellowbox on acceptsKeyboardFocus Fixes #498 This change adds support for the "focusable" property present in upstream RN, along with react-native-windows and NetUI. We need to reconcile this against the existing acceptsKeyboardFocus property. This is tricky since its usage was untyped. We follow the same strategy as react-native-windows for this. 1. Usages of acceptsKeyboardFocus will continue to work, but will yellowbox 2. Components will prefer to use focusable, and Touchables with slightly different semantics will prefer focusable semantics when present acceptsKeyboardFocus will redbox in RNW 0.64 instead of yellowbox, but this change should allow xplat code to use focusable and not be effected by that. Validated setting a view to focusable is propagated, and that acceptsKeyboardFocus is propagated with a yellowbox. * PR feedback * Explicitly false * Removed the wrong focusable...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
From Keyboarding in React Native Desktop document:
The text was updated successfully, but these errors were encountered: