🐛 fix(react): fix option selection with arbitrary values and search #1688
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
maximedasilva
approved these changes
Dec 16, 2025
dackmin
requested changes
Dec 17, 2025
dackmin
approved these changes
Jan 8, 2026
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.
This PR fixes a bug with the
<SelectField />( +allowArbitraryValues={true}andsearchable={true}) component where selecting an option does not update the field value with the selected option's one but with the searched term instead. It happens because the input's blur event triggers before the option's click. We now keep track of the option being clicked to prevent triggeringonSelectOption()from the internalonBlur_().Before :
Screen.Recording.2025-12-16.at.14.09.48.mov
After :
Screen.Recording.2025-12-16.at.14.10.46.mov