In particular, I recently ran into a very long-running issue where Chrom[ium] attempts to auto-fill inappropriate shit (like names from saved credit cards) into utterly unrelated form fields.
This has been going on for many years now [0], because maintainers insist their browser must ignore standards like autocomplete="off" [1] and use some "crowdsourced" remote-server fuzzy-recognition bullshit, and when their AI system is terribly wrong there's way for pages to opt-out.
This is especially aggravating for any developers who cannot meet WCAG accessibility guidelines that might be required of them by contract or law, and people have submitted a litany of other problematic examples [2] to no effect.
I can't comment on all of Chrome's behavior here, but Firefox ignores autocomplete="off" too, and this is noted on MDN [0]. This is because a lot of poorly-managed sites think they're being security-conscious by disabling password managers, so browsers had to step in and ignore the attribute.
I don't have a problem with any browser supplying credentials that the user has already used and chosen to save for a specific particular domain/form/input.
The issue is that Chrome is randomly/unpreventably suggesting all sorts of data even when field is for a medical patient's name rather than doctor using it, or when it's a generic chat-message field, and it does all that when the user has never used the form or even visited the domain before.
Informing all customers that it's out of our hands and can only be stopped by disabling their personal Chrome settings is... Not practical.
In particular, I recently ran into a very long-running issue where Chrom[ium] attempts to auto-fill inappropriate shit (like names from saved credit cards) into utterly unrelated form fields.
This has been going on for many years now [0], because maintainers insist their browser must ignore standards like autocomplete="off" [1] and use some "crowdsourced" remote-server fuzzy-recognition bullshit, and when their AI system is terribly wrong there's way for pages to opt-out.
This is especially aggravating for any developers who cannot meet WCAG accessibility guidelines that might be required of them by contract or law, and people have submitted a litany of other problematic examples [2] to no effect.
_____________
[0] https://issues.chromium.org/issues/40093420
[1] https://source.chromium.org/chromium/chromium/src/+/main:com...
[2] https://issues.chromium.org/issues/41239842