-
-
Notifications
You must be signed in to change notification settings - Fork 140
[Bug]: text search field value is not cleared after an option is selected #815
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
Comments
Maybe this should be a specific option as the default behavior might be useful when performing sequential and/or successive searches |
would like it to be optional as mentioned, as something you want to keep the search/filter active. Perhaps clicking outside the selection list (eg back in the main part of the select, or outside the control) could activate the clearing? |
I think it should be the default, like on the official website. It is unexpected to see "No results found" immediately after selecting a result. |
This issue has not been active in 120 days and has been marked "stale". Remove stale label or comment or this will be closed in 15 days |
still an issue |
Uh oh!
There was an error while loading. Please reload this page.
Bug description
When using the text search field in Tom Select.js, the entered search query remains in the input field after selecting an option. This requires the user to manually clear the existing text before searching for another option. No errors are logged in the console during this behavior.
Expected behavior
After selecting an option:
The correct behavior is observed everywhere on the official site https://tom-select.js.org/, but the person who wrote the example seems to have manually worked around the bug by adding the following to the options.
In my opinion, the behavior exhibited on the official site is correct and should be the default.
Steps to reproduce
Additional context
Intially reported in sqlpage/SQLPage#704
The text was updated successfully, but these errors were encountered: