-
Notifications
You must be signed in to change notification settings - Fork 531
autoHighlight is not always highlighting the top match #239
Comments
The current implementation is equivalent to |
@CMTegner - i see the line right here:
Why is it difficult to change it to something like:
|
It's not difficult, we just don't intend on changing the behaviour at the moment. When we eventually do, we will want to create something that is flexible enough to cater to different needs, and not just a single use case. |
@CMTegner - I've forked the repo, added a predicate support, which is essentially a function receiving It's not possible for me to create a fork since I've included the build files for our own modules, but should you desire, I can create one for you guys. |
@silicakes Would you be interested in submitting a PR with your changes to implement this? It seems like it should be expected functionality. |
I've found a "solution" for my use case, I just want it to select the first in the list by default, so that the user can hit enter and it will select the first in the list, for the getItemValue(item) just return the input query, that way the first always matches the default match and is selected until the user starts navigating with the arrow keys. |
The top match is only highlighted if it is compared to a String with the exact same beginning.
For Example if I want to search for "123" it will only be highlighted if I enter "1" and it is not being highlighted if I write "2" or "3" in the input field.
The text was updated successfully, but these errors were encountered: