Open
Bug 1960724
Opened 6 days ago
Updated 4 days ago
Show onboarding flow to all first time users (i.e. prevent the sandbox view from even being accessed until onboarding is complete)
Categories
(Firefox for Android :: Onboarding, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox137 | --- | fix-optional |
firefox138 | --- | fix-optional |
firefox139 | --- | affected |
People
(Reporter: vtay, Unassigned)
References
Details
(Whiteboard: [fxdroid] [tos])
Attachments
(1 file)
Expected behavior
We’d like all new Firefox users/first time users to go through the onboarding flow, even when they opened Firefox from other apps
Actual behavior
Users can currently bypass the onboarding flow by setting Firefox as the default (before explicitly opening the app) > opening a link > in the ‘sandboxed’ Firefox view menu > “open in Firefox”
Any additional information?
Please check that existing users who bypassed onboarding but open Firefox in a sandbox view do not have to go through the onboarding flow again.
Note: It would be nice to fix, but probably doesn't need to be rushed into last-minute beta uplift or a dot release
Updated•6 days ago
|
Summary: Show onboarding flow to all first time users → Show onboarding flow to all first time users ( i.e. prevent the sandbox view from even being accessed until onboarding is complete)
Updated•6 days ago
|
Severity: -- → N/A
status-firefox137:
--- → fix-optional
status-firefox138:
--- → fix-optional
status-firefox139:
--- → affected
Summary: Show onboarding flow to all first time users ( i.e. prevent the sandbox view from even being accessed until onboarding is complete) → Show onboarding flow to all first time users (i.e. prevent the sandbox view from even being accessed until onboarding is complete)
Comment 1•6 days ago
|
||
Updated•5 days ago
|
Assignee: nobody → joberhauser
Status: NEW → ASSIGNED
Comment 2•4 days ago
|
||
Unassigned John for now because we're postponing this bug to later.
Assignee: joberhauser → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•