3 ms·
Relevant reply from a Googler seems to be this: https://bugs.chromium.org/p/chromium/issues/detail?id=914451#c66 https://bugs.chromium.org/p/chromium/issues/det
by xg15 7y ago
Relevant reply from a Googler seems to be this: https://bugs.chromium.org/p/chromium/issues/detail?id=914451#c66 https://bugs.chromium.org/p/chromium/issues/detail?id=914451...
by battre@google.com
... which doesn't read at all to me like a "rogue dev" and more like a shared sentiment inside the Chrome team that autocomplete=off should be ignored.
At least, if there is a direct spec violation that breaks all kinds of applications and the answer your hear is "oh well, we're working on giving the user more options and improving our algorithm", that's not exactly encouraging.
- bullman 7y agoIt is a direct spec violation, and it is breaking all kinds of applications. Look, I get that this capability is super useful on shopping sites, and I rely on it practically every day. But, I also build enterprise applications, where Chrome simply would not ever understand or know what would be valid choice. I do, though; I built it. Invoice Numbers / Pre-Validated Travel Dates & Locations / Pre-Validated Locations / Pre-Validated IssueID that are so esoteric, we have built custom autocomplete that provide additional relevant information / Pre-Validated Users where the number of valid "John Smith"s number in the 10s, and additional meta data must be provided to differentiate. Application developers need a reliable, durable way to tell the UA that a particular field should never be autofilled or autocompleted. The spec says this is autocomplete=off. Just do that.