Allow editing of web site address of saved passwords
Categories
(Firefox :: about:logins, enhancement)
Tracking
()
People
(Reporter: john.mozilla, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
I have a saved username and password for website https://www.example.com/ which worked fine until the website re-factored itself and logins now use a different URL, e.g. https://signin.example.com/
Actual results:
Firefox doesn't autofill in the username and password. If you click in the form, it will offer the username/password as a suggestion, but this requires more clicks, which gets annoying after a while, especially if it's a site you use a lot! (Paper cut)
Expected results:
It would be good if there was an easy way for the user to correct this situation. At the moment, if they choose the suggested username/password, Firefox doesn't remember this next time. It would be nice if the user could tick something to tell Firefox to use this username/password entry from now on for the new URL.
Alternatively or additionally, in about:logins you can edit a username/password entry, but you cannot edit the URL to reflect the new site.
As far as I can tell, the only way to get Firefox to automatically fill in the username/password on the new URL is to actually delete the entry in about:logins, login, and save the new entry, which is not great UX.
Many thanks for reading this.
Comment 1•4 years ago
|
||
Mattn: we made a decision to treat the origin as the primary key and immutable in about:logins, but I don't actually recall the reasoning or if this decision was documented. This seems like an uncommon but not unreasonable feature request. Do you have any context?
Comment 2•4 years ago
|
||
We were trying to make a simple password manager for mainstream users, not target the same market as third-party password managers with advanced UX and bells and whistles. Editing the origin can cause passwords to no longer fill and most people wouldn't need to do that so that's why we didn't do it yet. The other issue is that users cannot edit the formActionOrigin
or httpRealm
so editing the origin
isn't necessarily going to fix their problems.
If there is good validation and the UX doesn't tempt users to edit it when they shouldn't then supporting this is fine but you'll need to figure out how to handle formActionOrigin
and httpRealm
too.
Description
•