-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
[Bug]: Remove delay before displaying results #734
Comments
I've also noticed this. I notice that selectize.js doesn't have this issue and there appears to be some minimal activity in that repo, even if it's mostly documentation related, so I decided to go with that one. |
This is not documented, AFAICS, but this can be addressed setting
Found it in the code: Line 26 in 69180fa
|
Nice find @pereorga! Can confirm it works in a codepen. One of us should make a PR to at least add this to the documentation, and maybe also default it to 0. |
I would be happy to do it if there was a chance it can get merged (unfortunately, the project seems a bit unmaintained at this moment). Meanwhile, people can find the solution here. |
Good find! |
Bug description
When answering a question about tom-select performance in Stack Overflow, I noticed there is a delay when searching. When not loading the data from a remote resource, results start appearing half a second later, no matter how many options the element has.
Expected behavior
Ideally, results should display immediately after key press. In other solutions (Selectize.js, typeahead.js, etc.) results appear immediately
Steps to reproduce
Additional context
The text was updated successfully, but these errors were encountered: