Closed Bug 1949883 Opened 28 days ago Closed 28 days ago

Set general.aboutConfig.enable in geckoview-prefs.js instead of in Java or Kotlin code.

Categories

(GeckoView :: General, enhancement)

Product:
GeckoView
Component:
General
Platform:
All
Android
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: sinker, Unassigned)

Details

We have several products are setting preference "general.aboutConfig.enable" through an aboutConfigEnabled() API.
If I am correct, It overwrites geckoview-prefs.js. And, it is not a preference supposed to be.
Let's move these changes to geckoview-prefs.js.

[duplicate comment from another bug]

The API method in question is exposed so that the apps could decide which channel to enable the setting on. That way, if Fenix decides they don't want about:config in Beta - it's up to them, they just change their code. Focus, meanwhile, can still allow Beta users to acces about:config.

If we use prefs - that will affect all the apps that embed GeckoView, and they won't have control over that (won't be able to change that programmatically in their own code bases independently from other apps, and won't be able to, say, expose a UI to make that changeable by user). We don't want that.

Status: NEW → RESOLVED
Closed: 28 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.