Closed Bug 1633125 Opened 4 years ago Closed 4 years ago

"Use Generated Password" right-click option is confusing

Categories

(Toolkit :: Password Manager, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1551723

People

(Reporter: standard8, Unassigned)

Details

The right-click option to "Use Generated Password" can be confusing because it implies you would be using an already generated password - 'generated' is in the past tense.

This would feel better if it was phrased as "Generate a Password", so that you know it is the future tense.

The "Use a securely generated password" pop-up is alright as it is because it has already generated, and shown you, the password.

(In reply to Mark Banner (:standard8) from comment #0)

The right-click option to "Use Generated Password" can be confusing because it implies you would be using an already generated password - 'generated' is in the past tense.

Sometimes that is the case since we cache the generated password for the session for that site+container. That allows you to fill the confirmation field with the same password as the original new password field. I guess bug 1569568 would address this issue.

This would feel better if it was phrased as "Generate a Password", so that you know it is the future tense.

You can only know that in some cases and I don't think it's worth the complexity to conditionally change the string. I hadn't really thought of this before though. Also keep in mind that if you saw the autocomplete suggestion but then used the context menu item you would still get the same password so I think the past tense makes sense in that case.

The "Use a securely generated password" pop-up is alright as it is because it has already generated, and shown you, the password.

True.

Unless you have a string that works in both future and past tenses simultaneously then I think this is wontfix or a dupe of bug 1569568.

Flags: needinfo?(standard8)
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(standard8)
Resolution: --- → DUPLICATE
Duplicate of bug: 1551723
No longer duplicate of bug: 1569568
You need to log in before you can comment on or make changes to this bug.