Firefox includes a Password Manager that can save the passwords you use to log in to websites. This article describes why your passwords might not be saved. For a general overview of using the Password Manager to save website passwords, see Password Manager - Remember, delete, change and import saved passwords in Firefox.

Hi, I noticed that iCloud Keychain does not offer to save the password from some sites when I use Safari on my Mac. I made sure that 'Allow AutoFill even for websites that request passwords not to be saved' is on. Safari on my iPhone and iPad mini offer to save the passwords for the same sites, so that works as expected. One of the sites on which I noticed this problem is this very site, MacRumors Forums. Power query in mac. I even went to create a new password, which Safari said it would save in iCloud Keychain, but it didn't. Anyone seen this too?

I'm a little confused; is this workaround to get safari to offer to CREATE a password, or to get safari to RETRIEVE a previously created password from its keychain? Either way, one can speak of how it is impossible to handle all cases, and sure the savvy among us can read through these forums and figure out workarounds, but if the system is so finicky that even macrumors apparently doesn't 'play right', then i think there is an argument to be made that apple's new keychain is not a 'solution' at all. A feature like this, especially for novice computer users, requests a high level of trust from its users ('let us make up a password to your account that even you don't know, but TRUST us that we'll remember it for you'), but then makes the apparent unspoken caveat 'the web is waaay to inconsistent to be sure this will work every time though, so good luck resetting your account or figuring out what went wrong the times it fails'. Click to expand.It may have something to do with the fact that this site's login form, as currently designed, runs some client Javascript in your browser before it gets submitted to the website when you hit the login button. The Javascript in question mangles the password that you typed and converts it into an MD5 hash.

However, if you click the reload button in Safari (as a workaround), this does not submit the form. In technical terms, it does a GET of the page rather than a POST. This will not result in any initial password mangling; Safari will recognise the form as worthy of remembering, and gives you the opportunity to save the username/password in keychain. Mangling passwords in the client's browser is not ideal, and there are more straightforward ways of achieving a secure login.

For example, many sites provide a secure (SSL) login page. Thus the password cannot be sniffed on transit. Then, on the site's server (NOT the client browser) a hash is computed and compared when the login form is submitted.