When an existing FXA user signs in, they are not sent back to the original Relay form with a new mask
Categories
(Toolkit :: Password Manager, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox132 | --- | fixed |
People
(Reporter: groovecoder, Assigned: groovecoder)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxcm-relay-all])
Attachments
(1 file)
STR:
- Be signed OUT of the browser
- Go to https://fill.dev/form/registration-email
- Click in the email input field
- Choose the Relay option in the auto-complete drop-down
- Choose to sign into an account and use a mask
- Sign into an EXISTING FxA
Expected results
After completing sign-in, you should be sent back to the tab & form field that started the FxA sign-in flow
Actual results
You stay on https://accounts.firefox.com/connect_another_device
I believe this is because the first implementation is only observing the ONVERIFIED_NOTIFICATION
event. It should observe an event when sign-in is completed.
Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Assignee | ||
Updated•5 months ago
|
Assignee | ||
Updated•5 months ago
|
Comment 1•5 months ago
|
||
Hi, per https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity:
S1 (Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, likely dot release driver, and no workaround available
Is that the correct severity for this bug?
Assignee | ||
Comment 2•5 months ago
|
||
Sorry, no. Changing to S3. I wasn't aware that severity was independent of other flags like "behind-pref". This is a serious bug for this feature, but this feature is behind a pref so it's not impacting any release users, let alone 25%.
Assignee | ||
Comment 3•5 months ago
|
||
Updated•5 months ago
|
Updated•5 months ago
|
Description
•