This repository has been archived by the owner on Feb 20, 2023. It is now read-only.
Don't hide "set as default browser" on Android 5 & 6 #5898
Labels
🐞 bug
Crashes, Something isn't working, ..
E2
Estimation Point: easy, half a day to 2 days
eng:qa:verified
QA Verified
Feature:FennecTransition
Comments
sblatz
added
🐞 bug
Crashes, Something isn't working, ..
Feature:FennecTransition
needs:group-triage
and removed
needs:group-triage
labels
Oct 9, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Oct 10, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Oct 10, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Oct 10, 2019
sblatz
added a commit
to sblatz/fenix
that referenced
this issue
Oct 10, 2019
Hi, I've check on the latest debug build from Master 1.0.1941 11/10 using the following devices: The "Set as default browser" section is indeed displayed on the other hand there is no redirecting made to the newly opened page (sumo article). Similar behavior trying to "disable" the toggle. @sblatz Please review and let us know if the user should automatically redirected to the sumo article. |
boek
pushed a commit
to boek/fenix
that referenced
this issue
Oct 16, 2019
5973: For mozilla-mobile#5898: Launch SUMO article properly for default browser r=colintheshots a=sblatz Co-authored-by: Sawyer Blatz <sdblatz@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
🐞 bug
Crashes, Something isn't working, ..
E2
Estimation Point: easy, half a day to 2 days
eng:qa:verified
QA Verified
Feature:FennecTransition
In #382 we hid the default browser toggle on these lower versions for MVP.
As suggested by Vesta, we should unhide this toggle and use it to link to the sumo article (which is what we did in Focus): https://support.mozilla.org/en-US/kb/how-set-firefox-preview-your-default-browser-android
This would also deal with #5870 as users could access that toggle.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: