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 component is created from an input field that can be autocompleted using the browser's built-in autocomplete (for example, selecting a country), tom-select behaves incorrectly.
The following description is provided for the country selection element.
Upon initial form filling, the value is correctly populated but not automatically selected.
Then, when a value is selected, clearing the form does not erase the value.
demo2024-03-15_13-55-16.mp4
If a value is selected and then another value is autocompleted, it is appended next to the previously selected value (presumably, it is inserted into the input located within the Tom-select component).
Additionally, it seems that Chrome ignores the autocomplete="off" attribute of the input embedded in tom-select.
I understand that there might be challenges in dealing with Chrome's behavior (such as ignoring autocomplete="off", tracking form clearing event). This issue is being raised in the hope that there are individuals with insights and expertise who can explore potential workaround solutions.
The text was updated successfully, but these errors were encountered:
When the tom-select component is created from an input field that can be autocompleted using the browser's built-in autocomplete (for example, selecting a country), tom-select behaves incorrectly.
The following description is provided for the country selection element.
Upon initial form filling, the value is correctly populated but not automatically selected.
Then, when a value is selected, clearing the form does not erase the value.
demo
2024-03-15_13-55-16.mp4
If a value is selected and then another value is autocompleted, it is appended next to the previously selected value (presumably, it is inserted into the input located within the Tom-select component).
Additionally, it seems that Chrome ignores the
autocomplete="off"
attribute of the input embedded in tom-select.demo
2024-03-15_13-55-57.mp4
jfiddle - https://jsfiddle.net/cheack/eLmn5dp7/1/
I understand that there might be challenges in dealing with Chrome's behavior (such as ignoring
autocomplete="off"
, tracking form clearing event). This issue is being raised in the hope that there are individuals with insights and expertise who can explore potential workaround solutions.The text was updated successfully, but these errors were encountered: