Open Bug 1548854 Opened 5 years ago Updated 2 years ago

Dedupe autocomplete rows offering a generated password and the auto-saved login row

Categories

(Toolkit :: Password Manager, enhancement, P3)

Product:
Toolkit
Component:
Password Manager
Platform:
Desktop
All
Type:
enhancement

Tracking

()

People

(Reporter: MattN, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [passwords:generation])

The user may need to re-enter a generated password into a confirmation field on the same page. There should be an autocomplete entry to allow the user to fill in the previously generated password. Right now we show the same autocomplete entry that is shown for the initial fill alongside any saved logins.

Edits to the generated password should also be reflected in what gets filled and shown in this autocomplete row.

Flags: qe-verify+
Depends on: 1548878

Hi Ryan, can you provide UX designs for this case?

Flags: needinfo?(rgaddis)

Per a conversation with MattN, this effort will be deprioritized in favor of automatically filling both fields first...

In the future, we'll look to supporting this manual fill via context menu or field dropdown (TBD).

Flags: needinfo?(rgaddis)
Summary: Add an autocomplete row to offer a password already generated on the page → Dedupe autocomplete rows offering a generated password and the auto-saved login row
Whiteboard: [passwords:generation]

Moving to P3 as this is not happening in the next release cycle.

Priority: P2 → P3
Severity: normal → S3

:imani lets see if we can close this one. We just need to exclude from autocomplete results entry that has no username and password equals to current generated password.

Flags: needinfo?(imani)
You need to log in before you can comment on or make changes to this bug.