Closed
Bug 1531164
Opened 6 years ago
Closed 9 months ago
autocomplete=username field should get username autocompletions when there is no password field
Categories
(Toolkit :: Password Manager, enhancement, P3)
Toolkit
Password Manager
Tracking
()
RESOLVED
DUPLICATE
of bug 1900009
People
(Reporter: MattN, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [passwords:fill-ui] )
<input autocomplete=username>
should provide username suggestions from saved logins in autocomplete instead of form history.
This would probably be easiest to implement like the existing type=password special case in nsFormFillController::StartSearch
(skipping markAsLoginManagerField
) and then teaching the password manager autocomplete search code that the field should be treated as a username field.
- The downside of this approach is that it means that if there are no saved usernames, the user won't get a form history fallback…
The chrome-only API GetAutocompleteInfo exists on <input> to get the parsed values. We can check that the fieldName
returned is "username".
Reporter | ||
Updated•6 years ago
|
Flags: qe-verify+
Comment 1•3 years ago
|
||
Moving to P3 as this is not happening in the next release cycle.
Priority: P2 → P3
Updated•3 years ago
|
Severity: normal → S3
Comment 2•9 months ago
|
||
Now that we have Bug 1900009 implemented all fields with autocomplete=username
should get the ac popup when we have a login in storage. Closing as duplicate of Bug 1900009
You need to log in
before you can comment on or make changes to this bug.
Description
•