Cache a generated login locally if there are existing saved logins for the site
Categories
(Toolkit :: Password Manager, enhancement, P2)
Tracking
()
People
(Reporter: MattN, Unassigned)
References
Details
When we fill a newly generated password for a user, we should make it available to be filled into other password fields (e.g. confirmation ones) and available to later prompt to save if there were saved logins for the site.
Rationale for not writing to persistent login storage: Since we can only save one password per username on a site, if there are saved logins for the site we risk overwriting them when the user may still need them to enter their old password.
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
Has this been implemented elsewhere? Is it intended that it's been resolved as WORKSFORME? Does it need to be verified (considering the qe-verify+ tag)?
|
|
Reporter | |
Comment 2•4 years ago
|
||
It was implemented in one of the first bugs in the project and you've already been verifying the related behaviour so I don't think it needs separate verification.
Description
•