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
{{ message }}
Repository navigation
[Feature Request] Clear v-autocomplete selection as soon as the text field is empty #5917
Case 1: If you delete all the text then you tab out, the v-autocomplete selection reappears.
Case 2: If you delete all the text then you hit 'backspace' or 'delete' (just once) and then you tab out, you will be left with an v-autocomplete with selected text that display's nothing.
Case 3: If you delete all the text then you hit 'backspace' or 'delete' (twice), the selection disappears.
It will be nice if as soon as the text field is empty, the selection dissapears.
This will inprove the ux and avoid having empty v-autocompletes with data binded.
Isn't the proposed solution still extremely dangerous for purposes of any forms where mistakes can have severe consequences? I strongly disagree with the default behavior of value de-selecting only after the input has been completely cleared. At the very least, this could be a parametrized behavior where we can choose if we want to clear the value on any change, even if the user only deletes a single character. As an extreme case, even if the user types the exact match, their input will still revert back to the previous & hidden internal value, which they may not notice.
I'm also tracking this, along with a related limitation of being unable to use a workaround, at
Activity
KaelWD commentedon Dec 18, 2018
This sounds like #4940
Anima-t3d commentedon Sep 3, 2019
KaelWD commentedon Sep 4, 2019
fix(VAutocomplete): remove selected item when input is cleared (#13854)
scscgit commentedon Apr 12, 2022
Isn't the proposed solution still extremely dangerous for purposes of any forms where mistakes can have severe consequences? I strongly disagree with the default behavior of value de-selecting only after the input has been completely cleared. At the very least, this could be a parametrized behavior where we can choose if we want to clear the value on any change, even if the user only deletes a single character. As an extreme case, even if the user types the exact match, their input will still revert back to the previous & hidden internal value, which they may not notice.
I'm also tracking this, along with a related limitation of being unable to use a workaround, at