61–70 of 383 posts
The Chrome dev team have implemented autocomplete the way they think it should work, not the way web developers want. You cannot switch off Chrome's handling of autocomplete, thus any other autocomplete implementation will be overwritten by Chrome's handling. Chrome team feel they know best.
I guess this will lead to a horrible coding style where instead of having this in the form: We will see stuff like this: Where developers use some type of abstraction that generates a random id for each field and then assigns it to the original value server side or in javascript. Just like they already randomise asset filenames to avoid caching.
It’s still a reasonably effective solution for CSRF, though there are much simpler options, but today’s bots largely have cookie jars so you will likely need a CAPTCHA.
Previously closed as WONTFIX: https://bugs.chromium.org/p/chromium/issues/detail?id=468153
https://bugs.chromium.org/p/chromium/issues/detail?id=587466
Overall, 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?
(And for the record: As a developer, I have been bitten by Chrome ignoring autocomplete="off" as well.)
Firefox used to ignore autocomplete="off" until relatively recently. I'm sick of sites thinking they know better than me -- like those who don't let me paste in the password field. While I understand the good use cases for this attribute, given the binary choice I would rather have it ignored.
Earlier quoted context omitted.
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.
You must have lived in a different past than me. IE was far more dominant, and browsers actually had meaningful differences back then. Porting CSS written for IE to Firefox could easily take 50% of the initial implementation time, if not 100%. Today, it's not completely uncommon to have something developed on Chrome working in Firefox and Safari without any changes. And the most significant problem with IE was obviou…
It doesn't matter if Chrome is open-source, when it is technically owned by a single corporation.
Earlier quoted context omitted.
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…
You just described reader mode!
These developers wouldn't be complaining if the Autofill functionality was activated by a toolbar button rather than automatically.