Open
Description
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
- Go to https://codepen.io/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-/pen/gbOLKKv?editors=1011
- Start typing something in the input
- Click outside the input
Additional context
- OS: all
- Browser all
- Version latest
- Device: all
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
lovasoa commentedon Feb 27, 2025
initially reported in sqlpage/SQLPage#832
lovasoa commentedon Feb 27, 2025
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.github-actions commentedon Jun 28, 2025
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