Suggestion: Hide advanced settings in developer options (about:config, sideloading, etc.)
Categories
(Firefox for Android :: General, enhancement)
Tracking
()
People
(Reporter: boek, Unassigned)
Details
From github: https://github.com/mozilla-mobile/fenix/issues/11639.
What is the user problem or growth opportunity you want to see solved?
Currently there are ongoing discussions between users and developers about which Fenix channels should receive what features (e. g. about:config, sideloading). To solve these issues and make advanced features available in every Fenix branch, I want to suggest the addition of (hidden) developer options, where the user is able to toggle these features on or off. Other browsers, e. g. Chromium, and the Android operating system itself already have hidden developer options, so this is a familiar feature for advanced Android users already and as far as I know these features have not caused damage to normal users of said programs.
These settings should at least include an option to enable about:config. Ideally there should also be preferences for enabling unsigned extension sideloading and some kind of debugging features (if needed).How do you know that this problem exists today? Why is this important?
There is a certain demand for advanced configuration options and features, which you can see in several issues across this issue tracker. Even though these features might not be useful for most users, they are an integral part for many Firefox fans, advanced and long-time users (which also recommend browsers to less tech-savvy people) and this functionality has existed for years already on Android (Fennec). It helps to make the migration smoother for all groups of users and prevents certain people from no longer upgrading their Firefox browser on Android or switching to other browsers that offer missing functionality (→ loosing more marketshare).
It also enables the possibility to revert about:config entries, which had been changed in Fennec, after upgrading to Fenix.Who will benefit from it?
Anyone with needs that exceed the needs of the average Firefox user and anyone that can't use Fenix because of missing preferences or walled gardens. Also developers (e. g. web developers, security researchers, maybe extension developers) who want to test certain features in all Fenix channels before shipping them to the end-user.
How does a similar feature look in other browsers?
UNITO-UNDERSCORE!20200616-143315!UNITO-UNDERSCORE!20200616-143341!UNITO-UNDERSCORE!20200616-143343!UNITO-UNDERSCORE!20200616-143358!
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Updated•2 years ago
|
Description
•