Issue 914451: Autofill does not respect autocomplete="off"
bugs.chromium.org
Issue 914451: Autofill does not respect autocomplete="off"
1–10 of 383 posts
Re: Issue 914451: Autofill does not respect autocomplete="off"
#2There was a time when IE was the dominant browser, and happily did whatever they wanted to.
That was arguably better, because at least they acted predictably. Chrome has been continually altering how autocomplete is handled in the last 5 or 6 major releases
Re: Issue 914451: Autofill does not respect autocomplete="off"
#3I would love it if someone explained how 'autocomplete=off' can lead to abuse of some kind. It seems to reduce the potential for security leaks.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#4There was a time when IE was the dominant browser, and happily did whatever they wanted to. That was arguably better, because at least they acted predictably. Chrome has been continually altering how autocomplete is handled in the last 5 or 6 major releases
The most horrible is that it is almost completely unstylable, last time I checked. If you have floating placeholders it gets fun.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#5Explanation from the 'rogue Chromium dev' is linked to in comment 19 of this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=914451...
https://bugs.chromium.org/p/chromium/issues/detail?id=468153...
Re: Issue 914451: Autofill does not respect autocomplete="off"
#6It's really frustrating to have to work around this with hit or miss hidden inputs and such.
So many cases too where auto complete misfires an obliterated forms that had helpful placeholder text.
Just having a user change passwords and auto complete will often put an old saved password in the first field but not the second confirmation password field.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#7I would love it if someone explained how 'autocomplete=off' can lead to abuse of some kind. It seems to reduce the potential for security leaks.
> It seems to reduce the potential for security leaks
Misguided views like this are exactly how. Turning off autocomplete doesn't improve any sort of security, since the site already needs to trust the browser.
It serves no purpose other than to frustrate the user, and might even reduce security if it prevents the user from easily making use of a password manager.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#8I would love it if someone explained how 'autocomplete=off' can lead to abuse of some kind. It seems to reduce the potential for security leaks.
It causes spec-compliant password managers to not work.
Unfortunately, disabling autocomplete for password fields is an often used form of security-theatre
Re: Issue 914451: Autofill does not respect autocomplete="off"
#9I would love it if someone explained how 'autocomplete=off' can lead to abuse of some kind. It seems to reduce the potential for security leaks.
> It seems to reduce the potential for security leaks Misguided views like this are exactly how. Turning off autocomplete doesn't improve any sort of security, since the site already needs to trust the browser. It serves no purpose other than to frustrate the user, and might even reduce security if it prevents the user from easily making use of a password manager.
plenty of stuff (like credit card info for instance) should absolutely never be auto-completed. The browser storing that sorta stuff to disk is stupid and completely avoidable.
Already caught chrome doing this to my Social Security Number before i disabled the functionality entirely. The idea of Chrome automatically auto filling any form it sees labeled "SSN" on any site dosen't inspire confidence.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#10I would love it if someone explained how 'autocomplete=off' can lead to abuse of some kind. It seems to reduce the potential for security leaks.
> It seems to reduce the potential for security leaks Misguided views like this are exactly how. Turning off autocomplete doesn't improve any sort of security, since the site already needs to trust the browser. It serves no purpose other than to frustrate the user, and might even reduce security if it prevents the user from easily making use of a password manager.
Agreed on password fields, however if you have a webapp crm it causes so many problems. And also giving a solution of "hey just put something that we don't understand in the autocomplete so we won't try to autocomplete it" is really not a solution at all.
Imagine if instead of autocomplete it was something like ignoring font sizes/color because they detected that engagement was low when font size was whatever so they render it differently. A browser should render HTML not make decisions like these