[docs] Clarify that fieldRef.current.focusField() is the canonical way to focus a field#22937
Merged
Merged
Conversation
…focus a field Signed-off-by: michel <[email protected]>
michelengelen
added
docs
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
LukasTy
reviewed
Jun 25, 2026
LukasTy
left a comment
LukasTy
left a comment
Member
There was a problem hiding this comment.
Nice direction. 👍
But maybe we should remove leftover usages in docs of inputRef.current?.focus() to better reflect this direction?
…in field demos Signed-off-by: michel <[email protected]>
Co-authored-by: Lukas Tyla <[email protected]> Signed-off-by: Michel Engelen <[email protected]>
LukasTy
approved these changes
Jun 30, 2026
LukasTy
left a comment
LukasTy
left a comment
Member
There was a problem hiding this comment.
LGTM. 👍
Very nice improvement. 💯
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
2 participants
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.
Follows up on #22592 (a v10 RFC for hidden-input focus delegation), which calls out that the docs should recommend fieldRef.current.focusField() over inputRef.current.focus() ahead of that breaking change. Adds a warning callout to the Fields docs, next to the existing imperative API demo, explaining why focusField() is the API to use.
Fixes #22592