Open
Bug 1119554
Opened 10 years ago
Updated 1 year ago
[meta] Revisit how the password manager captures login credentials during signup/registration flows
Categories
(Toolkit :: Password Manager, task)
Toolkit
Password Manager
Tracking
()
NEW
People
(Reporter: ckarlof, Unassigned)
References
(Depends on 2 open bugs)
Details
(Keywords: meta)
Attachments
(1 file)
9.62 KB,
image/png
|
Details |
It might be worthwhile revisiting how the password manager identifies a "signup" form. Signup forms present additional challenges vs login forms:
* Signup forms often have multiple non-password inputs, so we may capture the wrong value as the username.
* Signup forms sometimes use multiple password fields (to confirm the password), but not always.
* If the user already has saved credentials for the site, ideally we don't want to autofill those when the user is trying to sign up for a second account.
* Since password reset and change flows also use multiple password fields, it's possible our logic will get confused between these and signup flows.
Updated•5 years ago
|
Type: defect → task
Keywords: meta
Summary: Breakdown: Revisit how the password manager captures login credentials during signup flows → [meta] Revisit how the password manager captures login credentials during signup flows
Updated•5 years ago
|
Summary: [meta] Revisit how the password manager captures login credentials during signup flows → [meta] Revisit how the password manager captures login credentials during signup/registration flows
Updated•2 years ago
|
Severity: normal → S3
Comment 4•1 year ago
|
||
Note: we use SignUpFormRuleset.sys.mjs for this purpose now.
You need to log in
before you can comment on or make changes to this bug.
Description
•