3 ms·
>There's very few occasions when autocomplete being disabled makes sense True, perhaps. The point is that's not for Google to decide. In their example with CRM
by mrweasel 10y ago
>There's very few occasions when autocomplete being disabled makes sense
True, perhaps. The point is that's not for Google to decide. In their example with CRM system, it's very possible that the developer did think about it, and decided that autocompletion would "help" the user enter wrong data.
Now Chrome forces you to be non-compliant to work-around to their "custom feature".
Chrome is increasingly encouraging developer behaviour that's reminiscent of Microsoft and Internet Explorer 6.
- timdierks 10y agoIt's not for the developer to decide any more than the browser. It's up to the user.
- wmil 10y agoExcept there's no ability for the user to disable autosave on a page specific basis. So if autocomplete breaks functionality then there's nothing the user can do if the developer assumed autocomplete='off' would continue to work. Except disable autocomplete on every site, which is kind of overkill.
- dragonwriter 10y ago> So if autocomplete breaks functionality then there's nothing the user can do if the developer assumed autocomplete='off' would continue to work. Developers should not expect that things specced as hints will be treated as authoritative direction and should not make software that breaks if that unreasonable expectation doesn't hold.