FormTokenField: fix filtering with full-width string #70232
Merged
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.
Follow-up: #70180
What?
This PR normalizes user input from full-width characters to half-width characters internally.
Why?
In #70178, a process was added to normalize suggestions to half-width characters. This means that, for example, when searching for the half-width character string
WordPress
, it will match not only the half-width character stringWordPress
but also the full-width character stringWordPress
.However, we did not normalize user input. As a result, when a user searches for the full-width character string
WordPress
, the full-width character stringWordPress
included in the suggestions will no longer match because it has already been normalized to half-width characters.How?
Testing Instructions
Make the following changes and launch the
FormTokenField
orComboboxControl
story:Or add
WordPress
andWordPress
as post tags and open the post sidebar.Word
.WordPress
andWordPress
should match.Word
orWord
part should be in bold.Screenshots or screencast