Toolkit:Password Manager/Debugging: Difference between revisions

Line 22: Line 22:
* Logins are not auto-filled in '''Private Browsing''' windows. You should still be able to autocomplete the password from the autocomplete dropdown on the username field (if one exists).
* Logins are not auto-filled in '''Private Browsing''' windows. You should still be able to autocomplete the password from the autocomplete dropdown on the username field (if one exists).
* Logins are not auto-filled on insecure <code>http:</code> documents. Make sure all ancestor frames are <code>https:</code>
* Logins are not auto-filled on insecure <code>http:</code> documents. Make sure all ancestor frames are <code>https:</code>
* Logins are not auto-filled in sandboxed documents e.g. <code><iframe sandbox></code> or <code>Content-Security-Policy: sandbox;</code>
* If there are multiple username+password combinations saved for a domain and the username field wasn't pre-filled by the website, Firefox won't know which username/password to use and thus won't auto-fill. Use the autocomplete dropdown to choose the username you would like to use.
* If there are multiple username+password combinations saved for a domain and the username field wasn't pre-filled by the website, Firefox won't know which username/password to use and thus won't auto-fill. Use the autocomplete dropdown to choose the username you would like to use.
* If the page pre-fills the username field (e.g. using your session/local cookies or with a value attribute used as an old hack for placeholder text), Firefox won't fill in the password since the username field value doesn't match the one saved.
* If the page pre-fills the username field (e.g. using your session/local cookies or with a value attribute used as an old hack for placeholder text), Firefox won't fill in the password since the username field value doesn't match the one saved.
Confirmed users
933

edits