Bug 1585398 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I'd agree with you if bug 1576490 would be in scope for Fx70. As it is not, I'm afraid we are introducing "ifs" where a feature should be predictable: generated passwords are cached = 1 per session/principal  **unless** you update and merge your passwords, which would make perfect sense if we'd have bug 1576490. Add to the above the general usability concerns in bug 1570319.

If you choose to update and merge password in the change password mid-process, then you will actually have only the autocomplete to rely on, which would imply reaching a point in which you use your current stored password to update the password, not to mention you lose the convenient editable field in the case of generated password. 

Also, real edgy case, but it might be possible with this bug and bug 1584185 to reach a point mid password change where your current password, new password and re-entry password to be different.

Taking into account the fact that the vast majority of users have only 1 login/site, I would expect not having multiple generation per principal not to be such a big deal, while on the other side, we already have a complex enough feature, hard to understand for a first time user.
I'd agree with you if bug 1576490 would be in scope for Fx70. As it is not, I'm afraid we are introducing "ifs" where a feature should be predictable: generated passwords are cached = 1 per session/principal  **unless** you update and merge your passwords, which would make perfect sense if we'd have bug 1576490. Add to the above the general usability concerns in bug 1570319.

If you choose to update and merge password in the change password mid-process, then you will actually have only the autocomplete to rely on, which would imply reaching a point in which you use your current stored password to update the password, not to mention you lose the convenient editable field in the case of generated password. 

Also, real edgy case, but it might be possible with this bug and bug 1584185 to reach a point mid password change where your current password, new password and re-entry password to be different from the expected values.

Taking into account the fact that the vast majority of users have only 1 login/site, I would expect not having multiple generation per principal not to be such a big deal, while on the other side, we already have a complex enough feature, hard to understand for a first time user.

Back to Bug 1585398 Comment 2