Display "Set as default Browser" native prompt in home fragment
Categories
(Firefox for Android :: Experimentation and Telemetry, task, P1)
Tracking
()
People
(Reporter: vdreghici, Assigned: Gela)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][group2])
Attachments
(2 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-release+
|
Details | Review |
According to current criteria, the prompt will be displayed when the user lands on the home fragment.
Updated•10 months ago
|
Reporter | ||
Updated•10 months ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Comment 3•9 months ago
•
|
||
Backed out for causing HomeFragmentTest related fenix failure
This is also failing: https://treeherder.mozilla.org/logviewer?job_id=472773241&repo=autoland&lineNumber=3225
Comment 4•9 months ago
|
||
This also breaks org.mozilla.fenix.ui.HomeScreenTest#addPrivateBrowsingShortcutFromHomeScreenCFRTest
as the default browser prompt pop-ups on the private browsing screen blocking interactions of the test. Not sure if this is the new behaviour but the prompt should be disabled for UI tests (cc @andi).
Comment 5•9 months ago
|
||
Yes, we don't display the onboarding for this UI test and it looks like when we switch back the second time to the private browsing home screen the "Set as default browsing" dialog is being displayed.
Not sure if this should happen if the onboarding is being skipped by default ?
Comment 8•8 months ago
|
||
bugherder |
Assignee | ||
Comment 10•8 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D220189
Updated•8 months ago
|
Comment 11•8 months ago
|
||
release Uplift Approval Request
- User impact if declined: The native default browser feature will not be accessible in a 131 dot release
- Code covered by automated testing: yes
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: On Android 10 or newer after the 4th cold start we should see a default prompt asking users if they want to set Firefox as their default browser. On devices with older than Android 10, the behavior remains unchanged and they get a CFR instead.
- Risk associated with taking this patch: Low
- Explanation of risk level: Does not impact existing functionality drastically. Users on Android 10+ get a native prompt to set Firefox as their default browser.
- String changes made/needed: No
- Is Android affected?: yes
Comment 12•8 months ago
•
|
||
As Ryan suggested, I've added Bug 1916749 to the depends on field as these changes will break the UI tests.
Requested an uplift D223604 to land them at the same time.
Comment 13•8 months ago
•
|
||
Hello Gela and Aaron,
I tried this scenario on Android 10+ devices, in order to trigger the default prompt:
- Installed the Fenix Nightly 132.0a1 from Play Store (9/25 build).
- The "Set Firefox Nightly as your default browser app?" prompt was displayed over the onboarding.
- Tapped outside it, in order to dismiss it.
- Dismissed the onboarding, opened a tab.
- Force closed Fenix.
- Open a new tab, and force close Fenix 5 five more times.
- From the device's settings, moved the date & time with 3 weeks ahead.
- Reopened Fenix.
- No prompt displayed.
- Forced from the Secret Settings, by enabling "Enable Native Default Browser Promp for Existing Users" --> the prompt is displayed.
Tested this on a Google Pixel 6 (Android 15), Oppo Find N2 Flip (Android 14), and Xiaomi Mi8 Lite (Android 10).
On the Android <10, on Samsung Galaxy Note 8 (Android 9), and on a HTC 10 (Android 8), it works as expected:
- Installed the Fenix Nightly 132.0a1 from Play Store (9/25 build).
- Tapped on "Not now" on the "Set as your default browser" onboarding card.
- Dismissed the other onboarding cards, opened a tab.
- Force closed Fenix.
- Open a new tab, and force close three more times.
The "Set as default browser" banner is displayed on the homescreen.
Please let me know if I'm doing something wrong on trying to retrigger the "Set as default" propmt on Android 10+ devices.
Updated•8 months ago
|
Updated•8 months ago
|
Comment 14•8 months ago
|
||
Hi miralobontiu; I'll pass it over to Gela on this as I'm not familiar with the proposed changes.
Assignee | ||
Comment 15•7 months ago
|
||
Please let me know if I'm doing something wrong on trying to retrigger the "Set as default" propmt on Android 10+ devices.
Thanks for testing this, this feature was disabled by default and only becomes available after toggling it on in the secret settings menu. Rebeca just put up a patch to enable this by default which should go in as soon as mach try job succeeds: https://phabricator.services.mozilla.com/D224767
Updated•7 months ago
|
Comment 16•7 months ago
|
||
uplift |
Updated•7 months ago
|
Comment 17•7 months ago
|
||
Set as browser banner is correctly displayed on the latest Beta (132.0b4) and latest RC (131.0.1) builds on a Android <10 device (Samsung Galaxy Tab S3 with Android 9).
Set as browser prompt is correctly displayed on the latest RC (131.0.1) and on the latest Beta (132.0b4) builds on an Android 14 device (Samsung Galaxy S23 Ultra) through the above mentioned setting.
Marking the ticket as verified on 131 and 132.
Description
•