![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Update login info prompt fills in a bogus password
I use the save login info feature in Firefox. I have a saved login for a frequently used website. Firefox reliably fills out the username and password correctly for me. Recently it started asking me every time I log in to "Would you like to update this login?" prompt but with a bogus password. If I press "Update" it changes my password to this bogus password, so I have to press "Don't Update" every time I login just to keep my good password. If I do accidentally press "Update" I have to go to the "Saved Logins and Passwords" and manually fix my password for that website.
My question is, what would cause Firefox to think I have changed my password and give me this prompt when I have not?
And, by the way, the bogus password is always the word: "test" (my correct password is very strong and has over 20 characters).
Wybrane rozwiązanie
Reply to cor-el:
"Did you check the login form before and after sending the form in the developer tools (check DOM properties) ?" I'm not very familiar with developer tools to do this. I opened them but was unable to find anything. There are thousands of DOM properties and I have no idea which ones to look at.
"Other browsers may save/cache this data before the form is submitted, but Firefox waits until the form is actually send." This is a good explanation of why it behaves differently in Chrome.
"Did you try what I suggested above and edit the login data stored in Lockwise and create a block exception ?" Yes. This did solve this problem. Thank you!
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (7)
I would try to generate a new FF profile, run it and see if the problem is being caused by a corrupt profile. If the new profile doesnt generate the same issue problem solved. But becareful, you dont want to import the problem into your new profile. Let us know if you need step by step instructions to do this. cheers
Are you using any password add-ons?
Start Firefox in Safe Mode {web link}
A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
For the first reply from squirell, this did not solve the problem. I created a new user on my linux box, ran Firefox to create the new profile and tried to login to the website. Firefox still prompted me to save my login info with the wrong password.
For the second reply from FredMcD, this did not solve the problem. Starting Firefox in safe mode I still got prompted to save my login info with the wrong password.
Again, the password it want's me to save is always "test"
Some websites modify the login form via JavaScript when you submit the form to prevent browsers from storing login data or otherwise as a security measurement.
You can manually edit the password in Lockwise and create a login block exception to prevent Firefox asking to update the password.
Reply to cor-el: That was my thought as well, however, when I use Chrome I don't have this problem. This only happens in Firefox.
Did you check the login form before and after sending the form in the developer tools (check DOM properties) ?
Other browsers may save/cache this data before the form is submitted, but Firefox waits until the form is actually send.
Did you try what I suggested above and edit the login data stored in Lockwise and create a block exception ?
Wybrane rozwiązanie
Reply to cor-el:
"Did you check the login form before and after sending the form in the developer tools (check DOM properties) ?" I'm not very familiar with developer tools to do this. I opened them but was unable to find anything. There are thousands of DOM properties and I have no idea which ones to look at.
"Other browsers may save/cache this data before the form is submitted, but Firefox waits until the form is actually send." This is a good explanation of why it behaves differently in Chrome.
"Did you try what I suggested above and edit the login data stored in Lockwise and create a block exception ?" Yes. This did solve this problem. Thank you!
Zmodyfikowany przez cgrobertson w dniu