related, is there any way to actually shut it off via Chrome? I have the password manager disabled (supposedly) and using 1Password, but Chrome's version still pops up on login forms and interferes with 1Password.
Chrome does not respect autocomplete=off (2018)
81–84 of 84 posts
Re: Chrome does not respect autocomplete=off (2018)
#82Re: Chrome does not respect autocomplete=off (2018)
#83Earlier quoted context omitted.
The problem is that you’re only seeing angry developers and not the angry users frustrated that they can’t use autofill on sites that disable it for no real reason. Sites being able to change the behavior of the user-agent is almost always a bad thing. autocomplete=off should just be removed and it be entirely up to the user-agent whether it gets used like reader mode.
You've got to consider the 2nd order effects. Remove autocomplete=off? Developers will be forced to make their own DIY crappy text inputs just to get rid of it. And break everything but English input in the process.
I think these features should be like the notifications pop-ups “This site requested that Chrome not automatically fill out forms. Tap here to enable autofill anyway for this site.”
Re: Chrome does not respect autocomplete=off (2018)
#84Earlier quoted context omitted.
Especially when I'm pasting my routing number or bank account number. Like are you kidding me? I went into my bank app/website, I used the "copy" feature, and I'm trying to paste here AND into your "confirmation" field. Because I don't want to typo it! How could my copy skill be worse than my typing skill?
I'm on board with not allowing paste into a confirmation field since you might have copied the wrong number so there's nothing to gain from confirming the same mistake. Imagine you're doing several transactions and on one of them, you don't quite press the copy key correctly and end up using the previous account number from the clipboard.