Bad that chrome developers don't practice web development enough to know the use cases where ignoring autocomplete=off breaks the application.
Issue 914451: Autofill does not respect autocomplete="off"
31–40 of 383 posts
Re: Issue 914451: Autofill does not respect autocomplete="off"
#32A few years ago, I left a $1000 tip at the restaurant up the street because Chrome filled out the tip field with my zip code (which thankfully merely defaulted to max $1000 instead). The tip field was off-screen, and the ordering software didn't have a confirmation screen, just a "we just charged your card $X amount" screen, which made my eyes boggle. EDIT: Looking at the original March 17th, 2015 bug, it would have…
(How) did you resolve this?
Switched to Firefox.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#33Explanation 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...
...which really makes it worse: 1. Our programming language has an attribute called "autocomplete" with two possible values: "on" and "off" 2. We will now (without consultation or announcement) simply start ignoring one of those values when you specify it. (and certainly not document the new behaviour!) 3. Here, I made you a convoluted (and undocumented!) workaround for getting the original behaviour of the attribute…
I'm reminded of an earlier comment: https://news.ycombinator.com/item?id=21083277
Re: Issue 914451: Autofill does not respect autocomplete="off"
#34Does Chromium not have anyone doing QA or acceptance criteria? A rogue dev lead could make whatever feature they want, but there should be a robust process of testing by many people before the feature makes it in to a production build.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#35It's odd that the linked bug report references and complains about W3C specs when browser/HTML specs have been coming from WHATWG for well over ten years now. W3C has ceased publishing HTML with W3C HTML 5.2 in 2017, and has announced an intent to merely publish WHATWG snapshots going forward; so far, I'm not aware of any actual work under this model by W3C.
But OTOH that Chromium interprets form field names heuristically to enable auto-autocomplete is worrying, and reflects poorly on the whole "standardization" process by WHATWG.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#36Re: Issue 914451: Autofill does not respect autocomplete="off"
#37Because other people here are throwing in their frustrations, I will at least add that on the flip side I have been frustrated by sites that attempt to disable autofill for illegitimate reasons, like attempting to disallow password managers. I think I understand where this is coming from.
On the other hand, I, too, have been bit by this at least once, in the past. I think it was easier to just disable it at that time, but IIRC, the solution we landed on was to not use form controls at all but switch said text controls over to use content-editable elements. In our case it made sense, since it was not a form at all. My memory could be a bit hazy here, though.
(I do not work on Chrome or use Chrome at home, but as disclosure I do currently work at Google.)
Re: Issue 914451: Autofill does not respect autocomplete="off"
#38Overall, I still believe that neither of the extreme strategies ("always honor autocomplete=off"
Is it “extreme” now for a computer to do what the user wants and not what a random Google employee wants? How does this differ from malware?
Re: Issue 914451: Autofill does not respect autocomplete="off"
#39Earlier quoted context omitted.
They acted predictably by never updating IE and letting it stagnate. Hard to see how that is better in any meaningful way.
You still had a choice, nowadays being a Web Developer is almost a synonym for Chrome Developer and it was the IE hatting crowd that made it happen.
Except Chrome is still far below the user-base of IE in its heyday. And the most "valuable" users are all on mobile Safari. So it still makes sense to at least test with that.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#40I guess this will lead to a horrible coding style where instead of having this in the form:
Just like they already randomise asset filenames to avoid caching.