Chrome intentionally ignores "off" and "false" values for an input autocomplete attribute, to fit the WHATWG autofill standard (well... 'fit' their way).
Hence, v-autocomplete still prompts "autofilled browser suggestions" where their browser-autocomplete default value is "off".
Set the browser-autocomplete default value to something that doesn't match any WHATWG autofill standard, nor Chrome exception. Such as "disabled".
To keep the browser autofill behaviour, we would have to clearly define the prop to 'on' or to a WHATWG autofill token value.
In v2 the default autocomplete value has been removed.
I should probably make this a separate issue but with v2, the Chromium autofill sometimes shows suggestions for the v-text-field
, v-autocomplete
and v-combobox
. The browser autofill suggestions overlay the suggestions provided by v-autocomplete
and v-combobox
. Those two components should disable browser autofill functionality. It would be good if it was disabled by default with an option to enable it for v-text-field
though.
Most helpful comment
I should probably make this a separate issue but with v2, the Chromium autofill sometimes shows suggestions for the
v-text-field
,v-autocomplete
andv-combobox
. The browser autofill suggestions overlay the suggestions provided byv-autocomplete
andv-combobox
. Those two components should disable browser autofill functionality. It would be good if it was disabled by default with an option to enable it forv-text-field
though.