FF v31.0 - unable to update site login details
Hello,
After upgrading to FF for Android v31.0, I found that I can't change a saved site login username and password. I can enter the new details and login to the site, but these details are not being updated in FF. So the next time I visit that site, I'm shown the old details again.
How do I fix this?
Thanks. :)
edit: ammended title
Изменено
Выбранное решение
Ah there is an add on call Password Manager for the Andorid: link You can edit specific passwords, perhaps there are more than one for the site?
Прочитайте этот ответ в контексте 👍 1Все ответы (8)
When you go to a new website that requires a login, there will be a prompt from the url bar that says "Save password for "email" on "domain"" and you can choose to save or not save. This is where you can hit "save" and it will remember it.
If you do not want Firefox to remember the password you can forget this as well. You can do this automatically from the Settings > Privacy > "Remember Passwords" check box.
Hi guigs2.
The problem is that FF is not remembering login details when these have been changed (new password for an old site, etc..)
It shows (as mentioned) the previous login details - not the new ones.
Thanks.
So, does anyone else have a solution to this?
Thanks. :)
Try clearing the passwords in the privacy tab under settings. Then remember the password again for the site.
Please correct me if I'm wrong, but won't that clear ALL passwords?
That means I have to enter them all over again each time one of them changes? :(
Yes that will clear all the passwords. The only way to change stored passwords that I know if is on the desktop. If you use sync you can edit your passwords on the desktop and transfer it to your android.
Выбранное решение
Ah there is an add on call Password Manager for the Andorid: link You can edit specific passwords, perhaps there are more than one for the site?
Hi guigs2,
yes, that app works great. It enables me to work around the problem of FF not remembering an updated password.
Also, after adding this as a bug on bugzilla, I found that the nightly build of FF does not have this particular issue anymore. So, good news!
Thanks again. :)
Изменено