Provide a way to show password generation UI outside of `autocomplete="new-password"` fields

VERIFIED FIXED in Firefox 69

Status

()

enhancement
P2
normal
VERIFIED FIXED
4 months ago
23 days ago

People

(Reporter: MattN, Assigned: sfoster)

Tracking

(Depends on 1 bug, Blocks 1 bug)

Trunk
mozilla69
Desktop
All
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox69 verified)

Details

(Whiteboard: [passwords:generation] [skyline])

User Story

Some options discussed:
* Context menu item
* Option in autocomplete only when manually opened by the user with the down arrow
* Icon in the password field

Attachments

(2 attachments)

If an <input> DOES NOT have autocomplete="new-password", we don't have a strong signal that password generation is relevant for the field (e.g. this could be a login form) and so we should be more cautious about offering generation to the user.

Flags: qe-verify+

Hi Ryan, can you decide which UI we want to go with for manually opening the generation UI when we don't have confidence we're on a new password field?

Flags: needinfo?(rgaddis)
Posted image Context menu item

We'll start with the context menu for now.

Assignee: nobody → sfoster
Status: NEW → ASSIGNED
Flags: needinfo?(rgaddis)
Attachment #9073341 - Attachment description: Bug 1548391 - Add a contextmenu item to fill a password field with a generated password. r?MattN → Bug 1548391 - Add a contextmenu item to fill a password field with a generated password. r?jaws
Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fea496479a11
Add a contextmenu item to fill a password field with a generated password. r=jaws
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Regressions: 1564228
Whiteboard: [passwords:generation] [skyline]

Can confirm lack of the options with 69.0a1 (2019-05-29) .
As per comment 2; verified addition with 69.0b7 on Windows 10, macOS 10.14, Ubuntu 18.014.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.