Thanks, Chrome. So many sites have user-hostile code that is overridden by this choice. I still remember the glee when I first started using Chrome all those years ago, and suddenly all those forms filled themselves out.
[deleted]
Chrome does not respect autocomplete=off (2018)
11–20 of 84 posts
Re: Chrome does not respect autocomplete=off (2018)
#12Thanks, Chrome. So many sites have user-hostile code that is overridden by this choice. I still remember the glee when I first started using Chrome all those years ago, and suddenly all those forms filled themselves out.
I’ve seen autocomplete create plenty of problems. It can break some (admittedly poorly designed) forms outright. Or in others simply create a bad user experience. There are lots of forms that ask for an address but that should never be autocompleted to the user’s address.
In practice as a developer you have to resort to JavaScript hacks and obfuscating form field names to avoid it.
Re: Chrome does not respect autocomplete=off (2018)
#13Thanks, Chrome. So many sites have user-hostile code that is overridden by this choice. I still remember the glee when I first started using Chrome all those years ago, and suddenly all those forms filled themselves out.
I hate password forms that do this
I wish I didn’t have to disable clipboard events because of sites that think they know better to disable paste.
Re: Chrome does not respect autocomplete=off (2018)
#14(2018)
Re: Chrome does not respect autocomplete=off (2018)
#15Cool. Do paste blockers next.
Re: Chrome does not respect autocomplete=off (2018)
#16It’s pretty incredible to see the amount of steaming developers commenting on this issue. What tools do developers have, when platform providers turn a deaf ear to their needs?
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.
Re: Chrome does not respect autocomplete=off (2018)
#17[deleted]
Re: Chrome does not respect autocomplete=off (2018)
#18It is ironic that so many developers are taking the time to complain on the bug tracker but won't simply write Chrome out of their org. I did that at a place and most of the users didn't even realize something had changed.
No developers seem to have a problem simply refusing to support Firefox. I wonder how much extra effort it is going to take for them to finally make the switch.
Re: Chrome does not respect autocomplete=off (2018)
#19Thanks, Chrome. So many sites have user-hostile code that is overridden by this choice. I still remember the glee when I first started using Chrome all those years ago, and suddenly all those forms filled themselves out.
[deleted]
I mean, this is the place where Google and Apple can do no wrong.
Re: Chrome does not respect autocomplete=off (2018)
#20I’m not sure, but this might be related to my issues whenever I used chrome, and it would auto fill hidden elements of settings forms in pfSense. All of a sudden you had changed stuff you didn’t mean to, or get seemingly weird errors about invalid input.
At least I could imagine this prop being applied to hidden elements, either in pfSense or internally in chrome.