Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Ver 28 Problem saving password for a site

  • 3 replies
  • 1 has this problem
  • 4 views
  • Last reply by dkcrotty

more options

I have been trying to get FFox to save the password to a site and it is failing. I enter userID, password, have the save password checked and click login. Does not work.

I went to another site and tried it. It popped up an additional window asking me if I wanted to save the info. That one works just fine. This window did not popup on the failed site.

I checked the passwords that were saved. There were about 5(so it has been working). I accidentally clicked remove all, so woops on that. NP. Just start over. I have checked the options security is set properly (remember passwords for sites). I am not in a private browsing session. I can save cookies. I checked the exceptions. None. I don't have any additional password manager tools added. The only thing I have added to the original install was a theme. I just did that today, so the problem was before that. Now the password manager has the item that I just the one that I added.

So, it is working, just not for this site. And there is NOT an exception entered in the exceptions list.

That does raise one question/suggestion. In the password manager, add the ability to make a new entry. That would probably get by my problem

Using FFox 28, windows 8.1 pro 64 bit. The site I am using is www.sccrow.com. I created a userid guest and pw guestpw if anyone wants it to test. Its a site that is being built, so the content is nothing close to finished.

Oh yes. It isn't an issue caused by the site. It works in IE. The list below is correct on extensions.

I have been trying to get FFox to save the password to a site and it is failing. I enter userID, password, have the save password checked and click login. Does not work. I went to another site and tried it. It popped up an additional window asking me if I wanted to save the info. That one works just fine. This window did not popup on the failed site. I checked the passwords that were saved. There were about 5(so it has been working). I accidentally clicked remove all, so woops on that. NP. Just start over. I have checked the options security is set properly (remember passwords for sites). I am not in a private browsing session. I can save cookies. I checked the exceptions. None. I don't have any additional password manager tools added. The only thing I have added to the original install was a theme. I just did that today, so the problem was before that. Now the password manager has the item that I just the one that I added. So, it is working, just not for this site. And there is NOT an exception entered in the exceptions list. That does raise one question/suggestion. In the password manager, add the ability to make a new entry. That would probably get by my problem Using FFox 28, windows 8.1 pro 64 bit. The site I am using is www.sccrow.com. I created a userid guest and pw guestpw if anyone wants it to test. Its a site that is being built, so the content is nothing close to finished. Oh yes. It isn't an issue caused by the site. It works in IE. The list below is correct on extensions.

Chosen solution

Works for me.


The form uses autocomplete=off to prevent Firefox from saving form data like name and password, but in this case the form is in an iframe and the version of the bookmarklet on the squarefree.com site doesn't handle this case.

The version on the mozillaZine knowledge base size for iframes works (listed as the second bookmarklet), so you can use that version or use Inspect Element in the right-click context menu and change the autocomplete="off" to autocomplete="on" in both fields.

You can remove autocomplete=off with a bookmarklet to make Firefox store form data like names and passwords.

Note that Firefox won't auto-fill saved form data automatically when autocomplete=off is used, so you need to double-click the empty name field to get a drop-down list.

Read this answer in context 👍 1

All Replies (3)

more options

I have looked in the HTML and it seems like the password field should be recognised. However, I did notice that the submit button is just a link (<a> tag), rather than a <input type="submit" /> tag. Perhaps Firefox doesn't recognise the form as being submitted unless the button is properly labelled as a submit button. I also noticed that the link is to some JavaScript, rather than through the form's post method, meaning that this might be causing Firefox not to recognise when the form has been submitted.

more options

Chosen Solution

Works for me.


The form uses autocomplete=off to prevent Firefox from saving form data like name and password, but in this case the form is in an iframe and the version of the bookmarklet on the squarefree.com site doesn't handle this case.

The version on the mozillaZine knowledge base size for iframes works (listed as the second bookmarklet), so you can use that version or use Inspect Element in the right-click context menu and change the autocomplete="off" to autocomplete="on" in both fields.

You can remove autocomplete=off with a bookmarklet to make Firefox store form data like names and passwords.

Note that Firefox won't auto-fill saved form data automatically when autocomplete=off is used, so you need to double-click the empty name field to get a drop-down list.

Modified by cor-el

more options

Great. This worked. I would never have know that you could even do that, so it would not have been something that I figured out.

Note : double click works doesn't work after setting the autocomplete to "on" for both fields as suggested. I double clicked and waited 20 sec. repeated 5 times. Nothing. Then I rapid fire clicked for about 30 seconds. Nothing.

Finally, I discovered... Click the password field first, then back on the userId field. After that, it seems to work immediately and first time. I have to do this every time the form loads. Not a big deal.

Don't know if that is a bug, or what. Or if the whole thing can be fixed in the next version. But at least we have a solution.

Thank you for the response