3 ms·

nor should it. privacy settings should be up to user not the site.

• merlinscholz 6y ago
  This issue has (almost) nothing to do with privacy.
• jojobas 6y ago
  How does disabling auto-complete impact privacy? There are some examples in the thread - you can't have your address suggestion thingie display without Chrome's autocomplete on top of it.
• deleted 6y ago
  [deleted]
• kelnos 6y ago
  I think the purpose of autocomplete="off" is to allow an (honest, well-meaning) web site to tell a browser, "I know you think this looks like an address field, but it really isn't". Unfortunately, in reality, it's probably more often used to force users to type things in for misguided "security reasons". I think browser UI for this is generally just bad. I think forms should never auto-fill, but when I click on a form field, it should give me a dropdown to select text to put in just that field. Not that field plus all other fields in the form. Just that field. Then you don't have privacy issues (because the site never sees the autocomplete options unless the user actively selects one), and autocomplete="off" becomes unnecessary.
• hshshs2 6y ago
  It has nothing to do with privacy, and it may do the opposite. I’ve seen users accidentally submit forms with their phone number because we couldn’t turn off autocomplete and chrome decided something was a phone input (for no apparent reason). If a browser wants to provide autocomplete, they should implement it in a way that is safe rather than ignoring the spec. In this case we wanted to protect users from the mistake but couldn’t. Chrome took it upon themselves to run a basic web feature rather than implement better autocomplete.