Tom Select is a lightweight (~16kb gzipped) hybrid of a textbox and select box. Forked from selectize.js to provide a framework agnostic autocomplete widget with native-feeling keyboard navigation. Useful for tagging, contact lists, etc.
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.
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.
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.
Then, when a value is selected, clearing the form does not erase the value.
demo
https://github.com/orchidjs/tom-select/assets/91451120/6fc20a51-dc96-499e-9606-b8111bdd073dIf 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
https://github.com/orchidjs/tom-select/assets/91451120/9dfd2c21-9def-4ba1-8299-6b341d665bcajfiddle - 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.