Fix TagInput
adding a tag when Enter
is pressed while composing
#6767
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.
Fixes
The
TagInput
component has a built-inEnter
handler for adding a tag based on the current input value. This key is hit when composing languages such as Korean or Japanese, but not for the reason of adding a tag.The current implementation will both add a tag of the current value and keep the current value, which is unexpected behavior.
This implementation should ignore
Enter
keystrokes when the user is in the middle of composing.Checklist
Changes proposed in this pull request:
See above description.
Reviewers should focus on:
Whether or not we need to fix this in other places in Blueprint.
Screenshot