Make FxA Auth flow reliably wait before switching to Smart Window
Categories
(Core :: Machine Learning: Frontend, defect, P1)
Tracking
()
People
(Reporter: pdahiya, Assigned: markh)
References
(Blocks 1 open bug)
Details
(Whiteboard: [genai][onboarding][fxsync-])
Attachments
(1 file)
Scope of this bug is to ensure user completes FxA Auth flow before switching to Smart Window
STR
- Start Nightly and set pref
browser.smartwindow.enabledas true - Sign into Sync
- Click Switch to Smart Window and wait on Sign In Screen
- Click the account toolbar button while you're on the sign in screen to trigger FxA UI State update
Actual Result
User is taken to Smart Window without completing Smart Window Auth flow
Expected Result
User should enter credential and complete auth flow before switch
Issue here is Auth flow relies on UIState to check if a user is signed in before setting tos.hasConsent pref and redirecting to SmartWindow. UIState is FxA browser state and update can fire for other reasons outside of SmartWindow auth flow signin complete making it unreliable.
| Reporter | ||
Updated•7 months ago
|
Updated•7 months ago
|
Updated•6 months ago
|
| Assignee | ||
Comment 1•6 months ago
|
||
Smartwindow in particular wants to direct and already signed in
user to the login page for the "smartwindow" service. But an
already signed in user will in some cases cause fxaSignInFlow
to resolve before the flow is complete.
The other (unlikely but possible) scenario might be if 2
logins were active at the same time - eg, smartwindow is
logging in, and the user paused that and started a relay
flow login or similar.
I'm not sure what ipprotection does in the case of already signed
in users, but this patch should work in all cases.
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
Updated•6 months ago
|
Comment 5•6 months ago
|
||
Verified as fixed in our latest Nightly 149.0a1 (2026-02-09)
Description
•