You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
In my case I have a small number of alternatives that the user does NOT know beforehand. This causes a problem as the user can not see the alternatives until a first matching character is entered! I tried to modify the searchMinLength option but it made no effect.
After downloading the Tokenizer2 sourceode I found the following line that triggered my attention:
My interpretation is that the internal search command is not triggered unless the user input has at least one character. I think this should be modified to be:
This issue is back in the code again, any reason why? It is nice to be able to mouse in and have the drop down populate in some cases where the user doesn't know what to type to start.
Thanks, I still don't understand the reasons behind the && this.input.val().length > 0 being there AND searchMinLength being able to be set to 0, but anyways I removed && this.input.val().length > 0 from those 2 lines and set searchMinLength to 0 and it works perfect
The comment you point to is talking about adding an additional event click handler which is not really necessary.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In my case I have a small number of alternatives that the user does NOT know beforehand. This causes a problem as the user can not see the alternatives until a first matching character is entered! I tried to modify the searchMinLength option but it made no effect.
After downloading the Tokenizer2 sourceode I found the following line that triggered my attention:
My interpretation is that the internal search command is not triggered unless the user input has at least one character. I think this should be modified to be:
The text was updated successfully, but these errors were encountered: