-
Notifications
You must be signed in to change notification settings - Fork 407
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
Allow highlightOnlyResult
and selectHintOnEnter
with custom tags
#505
Comments
highlightOnlyResult
and selectHintOnEnter
with custom tags
Similar request in #526. I made the decision to disable those props when using custom option a long time ago, and I honestly can't remember why. At first glance, it seems reasonable to allow both, though there may have been some deeper issue with that. I'd have to take another look. |
For the |
For those coming across this from a search looking for the functionality described and seeing that
However this will only work for items matched in the array of known items, not for accepting any entered text as a new item when |
The short version is to let
highlightOnlyResult
work withallowNew
-- especially for the new entry.I'm creating tags. There's a list of existing tags that I've prepopulated into the
options
. But, I also want to allow new tags to be created withallowNew
. I want the user to be able to use the ENTER key to select the (existing) tag that he's started to type. UsingselectHintOnEnter
does a good enough job for this. But, if the user wants to add what he's typed as a new tag, he can't just ENTER.I think that this is normal behavior in other places. I feel like the "standard tag interface" (if there is such a thing) works this way. Type - ENTER - type - ENTER - type - ENTER. If the tag already exists, great. If not, still great. Right?
The text was updated successfully, but these errors were encountered: