3 ms·

Presumably this: https://bugzilla.mozilla.org/show_bug.cgi?id=956906 https://bugzilla.mozilla.org/show_bug.cgi?id=956906 I think it means that sites can't over

• dao- 11y ago
  > The argument seems to be the browser makers will store passwords safely. Not quite. Unless you set a master password, whoever owns your computer will own the passwords stored by your browser. The argument is that disabling autocomplete makes users choose poor passwords that are easy to remember, or write passwords down somewhere, which is at least as bad as having passwords stored in your browser profile.
  • quadrangle 11y ago
    writing passwords down somewhere, such as on PAPER, is not a particularly bad idea unless you keep the paper by your computer.
• sandstrom 11y ago
  There are some valid use-cases, e.g. in web-apps with an user-admin section. It's useful that when adding user 2 (or N) it won't auto-fill with details from the previous user (that you just added). If anyone has that issue, a workaround is to add multiple email/password inputs (dummies) around the real-one, and hide them. In Chrome, this causes it to 'give up' and not try to auto-fill the fields.