Expand support for non-prior defined prefs
Categories
(Firefox for Android :: Experimentation and Telemetry, task)
Tracking
()
People
(Reporter: olivia, Unassigned)
References
(Blocks 1 open bug)
Details
As of 03-25-2026,
If you attempt to set an undefined pref using the Nimbus - Fenix - Gecko preference experimenter setter, for example some.undefined.in.gecko.pref, then the experiment is rejected during preference setting and not enrolled. However, with the API it is possible to set arbirtary prefs and GeckoView supports this behavior.
Right now, we rely on the Gecko type of the pref to permit setting by retrieving information about it. Nimbus should provide the type and we be able to set arbitrary prefs given that information. See setGeckoPrefsState.
This bug or another bug should adjust the parsing so that we get correct real types.
|
Reporter | |
Updated•2 months ago
|
|
|
Reporter | |
Comment 1•2 months ago
|
||
I did some testing and I think it is important to note, it appears the current system will pickup prefs defined in geckoview-prefs.js just fine. So it appears any defined pref will set as expected, not just StaticPrefList.yaml.
Description
•