Closed
Bug 1427848
Opened 7 years ago
Closed 7 years ago
Password manager does not sync username when selecting a password
Categories
(Toolkit :: Password Manager, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: booc0mtaco, Unassigned)
Details
Attachments
(1 file)
59.70 KB,
image/gif
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/604.4.7 (KHTML, like Gecko) Version/11.0.2 Safari/604.4.7
Steps to reproduce:
Setup
1. Navigate to https://jsfiddle.net/oo8bsq7b/
2. Enter any username / password and press submit
3. "save" this login
4. repeat 1-2 times to save a few username/password combinations
Bug:
1. Select a username from the password manager (e.g. test1)
2. Clear the password that gets repopulated for that account
3. click in the password field, triggering the password manager , and select a different username/password combination (e.g., test2)
Actual results:
Observe that the password field is populated with test2's password, but the username field retains the original value (e.g. test1).
Expected results:
If you select a username/password combination from the password manager, it should always keep those two fields in sync. In this case, if you empty the password field and select a different saved account, it should update BOTH the username and password fields. There's no clear use case for using one saved account's password with a different username.
(I've opened a similar issue for chromium here: https://bugs.chromium.org/p/chromium/issues/detail?id=796988)
Reporter | ||
Comment 1•7 years ago
|
||
GIF demonstrating username/password field behavior
Updated•7 years ago
|
Component: Untriaged → Password Manager
Product: Firefox → Toolkit
Comment 2•7 years ago
|
||
This is intentional behaviour since detecting the username field often relies on heuristics and we don't want to overwrite an unrelated field with the username for the second fill.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•