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
When the tom select field is blurred, tom select reinitilizes it to an empty state, but still lets a change event bubble up the DOM, while the <select> element value is still the user's search string (that did not match any valid option).
Screencast.From.2025-02-27.15-24-57.mp4
Expected behavior
When the input field is reinitialized, and it was originally empty, then the value did not change, and no change event should bubble up to the parent form component.
Maybe the additional <input> element that tom-select creates to handle user input should not be linked to the same <form> element as the actual <select> that contains the real values selected by the user.
Bug description
When the tom select field is blurred, tom select reinitilizes it to an empty state, but still lets a
change
event bubble up the DOM, while the<select>
element value is still the user's search string (that did not match any valid option).Screencast.From.2025-02-27.15-24-57.mp4
Expected behavior
When the input field is reinitialized, and it was originally empty, then the value did not change, and no change event should bubble up to the parent form component.
Steps to reproduce
Additional context
The text was updated successfully, but these errors were encountered: