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.
Issue 914451: Autofill does not respect autocomplete="off"
51–60 of 383 posts
Re: Issue 914451: Autofill does not respect autocomplete="off"
#52Is "ignoring the specification" an extreme, now?
Are we seriously expected to entertain this mess?
So glad I switched to Firefox all those years ago.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#53Earlier 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.
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 obviously that it wasn't FOSS, and was only available for Windows. Neither applies to Chrome.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#54Earlier 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.
I seriously can't wrap my head around why anyone decided it would somehow be 'okay' to use googles web browser. Because unless you are a Pollyanna coolaid drinker you know where that's going to lead us.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#55Because 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…
I think we need a way to disable features only for those developers that abuse them. Like uMatrix but built-in and with rules being supplied automatically as ad blocking lists are.
You autocomplete=off a password field? That attribute won't have an effect on your site anymore.
You auto-play videos when the user doesn't expect it? What videos? The web doesn't support videos – as far as you are concerned.
Scroll hijacking? I hope you used progressive enhancement because you just lost your Javascript privileges.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#56Re: Issue 914451: Autofill does not respect autocomplete="off"
#57Earlier quoted context omitted.
Chargeback.
Is that allowed given that you appear to have authorized it and they have proof (it's obviously not fraud or something like that)?
Of course it's allowed. It would be under one of the Merchant Error chargeback codes since the intent was never there to tip $1000 (and it happened due to an error in their software).
If it's not classed under that code there's also 'Friendly Fraud' code for misrepresentation.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#58I 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.
I think some people want to be able to override it because some sites try to block password managers from filling the password field. Since Chrome has a built in password manager, that is likely their motivation to ignore it.
Re: Issue 914451: Autofill does not respect autocomplete="off"
#59The 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.
When i see something like this, i also remember that Google is basically a private "spy" company, that benefits the most by having all the data they can of each one of us.
So my feeling is theres must be a lot of pressure inside Google management to not let such a feature be turned of, giving this get sent to the 'mothership' as you type, with the lag you take, fingerprinting etc..
Its a big problem that a company that does what Google do, owns the most popular browser client and the most popular mobile OS where they can serve the interests of the mother company against our own self interest where we want our privacy and major political and civil freedoms respected in the process.