about:config doesn't work in Firefox Release

[jrmuizel]

This works in Nightly but not in release. This makes it very difficult to ask users to change settings for debugging purposes.

┆Issue is synchronized with this Jira Task

[filips123]

I would also like about:config support in stable releases. Fennec has it, so lack of it could be considered as one step backwards (although I agree that Firefox Preview has a lot of other improvements).

Also, about:config is not only needed for "debugging purposes." There are a lot of other useful things that can depend on about:config. For example, changing some more advanced settings, enabling/disabling some APIs (could be also used for security/privacy reasons), as well as other things.

So I would consider about:config support as quite important feature which should be enabled in stable releases.

[da2x]

I found bz#1540065 from a year ago that says:

“We've decided to add a GeckoRuntimeSetting that will control whether or not about:config is exposed. Fenix will use this to enable about:config in all scenarios.”

So it sounds like it should be available on all release branches including stable.

[boek]

We currently have it enabled in Nightly. Keeping this open as something to consider in the future

[andreicristianpetcu]

about:config is really useful for the SUMO community since new features might break some sites. TLS versions, same site cookies and various other things can be turned off to pinpoint the cause of an issue. Average users tend to have release, not beta or nightly.

[mcl21014]

about:config can be abused by some users, so maybe instead of punishing us all by removing the feature, show a more scary warning or something every time that cannot be permanently hidden. On one hand, you do not want less informed people creating bug tickets for experimental flags, but some people know what they're doing. I turn on privacy.resistfingerprinting to disable some tracking related to the browser header. I also disable the disk cache and set the memory cache capacity to -1, so it's dynamic since RAM is cheap as of late and I have a phone with 8GB RAM that is not being fully used. Also I increase the extension update interval, so I don't have to wait forever for an update to my extensions. Not much, but there's my usage case. And I prefer the stable branch. Even if the devs decide to not include it, maybe make it so we can easily build it ourselves with about:config. I can build and sideload APKs via ADB. Also I myself (many years ago) used to turn on entries I shouldn't, but I learned when everything crashed. Never blamed the devs or software. No reason to blame software for user error and remove a feature with that in mind.

[techboyg5]

about:config can be abused by some users, so maybe instead of punishing us all by removing the feature, show a more scary warning or something every time that cannot be permanently hidden. On one hand, you do not want less informed people creating bug tickets for experimental flags, but some people know what they're doing. I turn on privacy.resistfingerprinting to disable some tracking related to the browser header. I also disable the disk cache and set the memory cache capacity to -1, so it's dynamic since RAM is cheap as of late and I have a phone with 8GB RAM that is not being fully used. Also I increase the extension update interval, so I don't have to wait forever for an update to my extensions. Not much, but there's my usage case. And I prefer the stable branch. Even if the devs decide to not include it, maybe make it so we can easily build it ourselves with about:config. I can build and sideload APKs via ADB. Also I myself (many years ago) used to turn on entries I shouldn't, but I learned when everything crashed. Never blamed the devs or software. No reason to blame software for user error and remove a feature with that in mind.

OK, try adding "This might void your warranty" warning.

[stefankeys]

about:config is pretty useful and makes firefox more customizable. I think that as long as there is an easy way to reset all the settings to default it shouldn't be a problem. I don't see why the option to disable the warning should be removed though.

[techboyg5]

about:config is pretty useful and makes firefox more customizable. I think that as long as there is an easy way to reset all the settings to default it shouldn't be a problem. I don't see why the option to disable the warning should be removed though.

Well there isn't even a warning in the first place.

[lindongbin]

It's time to enable about:config on all versions.

[filips123]

I created enhancement request on Bugzilla for GeckoView to display warning when opening about:config. With that warning (similar to desktop one), unexperienced users will be warned that changing preferences can break things so about:config could be enabled on all versions without too much danger to users.

Also, can we get any confirmation from devs if they would consider enabling (and then enable) about:config on stable once that warning is added/displayed?

[freebrowser1]

I agree: about:config should remain in final release of Firefox Fenix with a warning 'this voids your warranty' or something alike, like the desktop/laptop version.
I entered a duplicate ticket not knowing this one already existed.
#12288

[nbmrjuhneibkr]

about:config has real use cases that have nothing to do with debugging. Users shouldn't be forced to use unstable builds to have access to these settings.

[chris-blay]

I'd like to configure layout.css.text-decoration-skip-ink.enabled = false for accessibility purposes in Fenix 79 (stable) but am currently unable to access about:config. Please help!

[crisalis2]

I won't use Fenix if I can't access about:config, and no, I'm not using as a main browser a beta or nightly version where stability is not as good and telemetry is most likely enforced. Please reconsider this. Even Chrome has access to the flags.

[jawz101]

###I can see the stance of Mozilla but I also have these things to say about about:config

It needs documentation surfaced within its ui. Both users and Mozilla devs would benefit from this.

eg.

0 - enables
1 - disables
2- etc...

It also needs constraints on what values you can use

if the only values that are applicable are 0,1,2 why can I put a 99999999999999 in the field?

if an acceptable range is 0-15000, why should I be allowed to use 999999999999 at all?

Why can I set apz.max_velocity_inches_per_ms to 'apple'?

This is a bandaid rather than giving that screen more refinement.

prefs should be limited to only those applicable to the platform.

prefs stagnate in about:config. Devs surely focus on their on a niche component and cannot see the utility in why some config settings even exist. A lot of development went into pieces that never see the light of day.

gfx.color_management.enablev4 has been a feature that has been in Firefox for maybe a decade, adds additional color information to photos, yet just sits there.

privacy.first_party_isolate, privacy.resist_fingerprinting, security.mixed_content, etc. prefs are all beneficial to privacy but they aren't surfaced in the main options ui.

And finally, some things should simply be deprecated, locked, or hidden as configurable.

Do I really ever need to toggle network.websocket.allowInsecureFromHTTPS? Has anyone even done this once?

Scrutinizing about:config, as with any other component, would reveal benefits that are not just for the sake of dressing it up. It can land features someone already fleshed out, surface others in the settings ui, find active use cases, harden the browser, and find new cases for enterprise policies.

Check out about:policies#documentation in the address bar. about:policies is a way to toggle prefs to limit or standardize Firefox when deploying it to thousands of computers in a company. If there are pref changes that are commonly set with prefs not already available as a policy, you can introduce more options to this configuration mechanism for wider deployments (e.g. say I deploy Firefox in a kiosk mode that prevents customizing the toolbar and theming. That may be worth a policy option.)

[ghost]

The socks proxy feature is important in the about:config settings. So please do have a quick release:)

[freebrowser1]

Anyway, why is Mozilla releasing an actually beta release which is not finished and advertized as 'official' and 'customizable' ?
This version is not finished at all when it lacks about.config and most extensions. So it is far less customizable than FF 68.11.
A software product like Firefox is for the users not for the developers, and here it appears the other way around.

And here I repeat the text of [mcl21014] which I got in my mail and I fully agree, but is probably modded away.

I deep down think it's insane that about:config is blocked in the stable for Android. Stable Chrome that ships with Android lets me go to chrome://flags, heed the warning, and break the browser if I want to. I have broken it with flags before, but guess what? I reverted them after reading documentation via another browser. So Firefox is taking an anti-user, anti-customization stance, and should think things over before shooting it's remaining users and itself in the foot. There's a much more unfiltered version of what I wanted to say. I mean no hatred of Firefox or anyone that works on it, but dang it we're not babies. I've used Firefox for some 12 years as my default and after every stupid move I want to switch to VIvaldi or something else. Take heed, developers, for ignoring users too much backfires as they switch and monetization goes down (from search deals). Mozilla is hurting now and with it's services not taking off it cannot afford to damage itself in various ways. Politicized snippets in the desktop browser are another example. Stick to making a browser and doing a good job of it. Not crippling features and dabbling with politics. It's for the best of the future of Mozilla corporation. Because corporations need revenue, derived from the consumer, to survive. I am upset for the case of the future of the company, and I don't even work there. Just please, go back to your roots and make money at the same time. Or thing will continue to worsen.

[klint]

A software product like Firefox is for the users not for the developers, and here it appears the other way around.

My 2 cts here: I understand your frustration (which I share to some extent), but it also can be that Mozilla is exactly doing what you stated in a first place: a software product for the users not for the developers :)
Or maybe stated in another way: a product for the average user not for the power users (in an attempt to extend the user base?).

For it seems to me that about:config and very specific addons are not really critical to the regular users, while the already released addons are enough for this type of user.

So, regular users are being served first at the moment, and power users like you and me will just have to wait a little bit for their favorite features to be back.
Please be patient, and you can still go back to FF 68 til then if the missing features are that critical to you.
:)

[helohe]

you can still go back to FF 68 til then if the missing features are that critical to you.
:)

Downgrading unfortunately does not seem to be that easy, especially on non-rooted phones. Just trying to install an older version of the apk did not work for me. I meanwhile forked the repository though and changed to get the about config back, may compile it myself and install it, that should work for now.

[freebrowser1]

A software product like Firefox is for the users not for the developers, and here it appears the other way around.

My 2 cts here: I understand your frustration (which I share to some extent), but it also can be that Mozilla is exactly doing what you stated in a first place: a software product for the users not for the developers :)
Or maybe stated in another way: a product for the average user not for the power users (in an attempt to extend the user base?).

For it seems to me that about:config and very specific addons are not really critical to the regular users, while the already released addons are enough for this type of user.

Is there ever made a poll ?

So, regular users are being served first at the moment, and power users like you and me will just have to wait a little bit for their favorite features to be back.
Please be patient, and you can still go back to FF 68 til then if the missing features are that critical to you.
:)

These addons and about:config are not so specific as Mozilla thinks.
Read the surge of negative comments on the Play Store.
https://play.google.com/store/apps/details?id=org.mozilla.firefox&hl=en&showAllReviews=true

And a FF with all add-ons and about:config still works for the regular user who don't use this.
This is another proof that this Fenix is far from ready and still in beta stage.

And, otherwise, release a Firefox 'light' (which is actually this Fenix release) for 'regular' users and an updated 79 or 80 'pro' with the same code base as the macOS / Windows / Linux edition just like FF 68 for Android.
But most 'regular' smartphone users use the builtin browser (usually Chrome) if they use a browser at all instead of 'dedicated' apps.

[freebrowser1]

Why so many thumbs down ?

[cadeyrn]

Why so many thumbs down ?

Probably because your comments are disrespectful to the developers and not constructive or helpful at all. You should think more about your words… It's possible to express your agreement to a proposal in other ways. And deliberately quoting deleted content is really not okay…

[jawz101]

Why so many thumbs down ?

Probably because your comments are disrespectful to the developers and not constructive or helpful at all. You should think more about your words… It's possible to express your agreement to a proposal in other ways. And deliberately quoting deleted content is really not okay…

They weren't disrespectful. I can think of a lot of ways to be disrespectful

[cadeyrn]

They weren't disrespectful.

I don't know if you're kidding but to say that the product is "not finished at all" or "Firefox is taking an anti-user, anti-customization stance" is very disrespectful to the developers and not helpful in any way.

[hwinnemoe]

I did find this answer by a Mozilla developer to be quite helpful: https://www.reddit.com/r/firefox/comments/i51k0q/mozilla_could_turn_on_about_config_and_have/g0n9nn0/

[freebrowser1]

They weren't disrespectful.

I don't know if you're kidding but to say that the product is "not finished at all" or "Firefox is taking an anti-user, anti-customization stance" is very disrespectful to the developers and not helpful in any way.

"Firefox is taking an anti-user, anti-customization stance"

Those are not my words, but words in the quoted text. And with such words I disagree as well. FF is not taking an anti-user / anti-customization stance to my opinion, but that the product is not finished, sorry, but that is my opinion. Still too many bugs for an 'official' version. Release should be postponed. And this is not disrespectful, it is just a comment on the product and there is Github user feedback for. This topic is about the deliberate omission of a useful feature about:config which frustrates many users, including me.
It is like an automaker omits aircon in a new car model because 'most cars are not sold in a hot climate'.

"klint" commented:
So, regular users are being served first at the moment, and power users like you and me will just have to wait a little bit for their favorite features to be back.

where he admits that the product is not finished yet.

[klint]

"klint" commented:
So, regular users are being served first at the moment, and power users like you and me will just have to wait a little bit for their favorite features to be back.

Hey, you can quote me but the conclusion is yours! I'm have no problem with the fact that normal users (existing or new ones) are being served first, with more advanced legacy features being rolled out later (or even never if there is a strong reason for it).

Anyway, you are true in a way, Firefox will never be "finished", it is an ongoing Agile process, like the Desktop version.

[freebrowser1]

Anyway, you are true in a way, Firefox will never be "finished", it is an ongoing Agile process, like the Desktop version.

And that is the difference: the 'desktop' version does contain about:config and the Android version not, despite being technically possible as the beta version of the Android version shows. Hence I use the beta version because it is more complete.

[opusforlife2]

Firefox Nighty

Okay, this really needs to be part of official Mozilla merch. Mozilla, please sell Firefox nighties! :P

[Dakkaron]

When talking about regular users vs power users, consider this: how many regular users switch their browser on Android on their own accord?

I would guess that most regular users who switch their browser do so, because a power user recommend it. So if you manage to ged rid of your power users, there is not much to gain.

And the last change was purely bad for power users (about:config blocked for no real reason without workaround, and also tons of addons blocked for no reason).

Considering how well the last few major changes went for Firefox, it appears as if they really don't want an user base to begin with...
And posts like this don't help convincing the users otherwise: https://twitter.com/EmilyKager/status/1289308930972278789

[hwinnemoe]

And the last change was purely bad for power users (about:config blocked for no real reason without workaround, and also tons of addons blocked for no reason).

Please read https://www.reddit.com/r/firefox/comments/i51k0q/mozilla_could_turn_on_about_config_and_have/g0n9nn0/, there are several reasons for this decision.

[yump]

@hwinnemoe The worst-case scenario dblohm7 describes is having to reinstall the app, which results in the loss of all open tabs and, if you didn't have sync enabled, all profile data. Coincidentally, that's very similar, although less reversible, to what happens if you switch between release Fenix and beta or nightly, or between release Fenix and F-Droid Fennec. And "use Beta/Nightly instead" is a common Reddit suggestion in response to complaints about Fenix.

[Dakkaron]

Wouldn't it be much easier to offer an about:config reset to default on crashes?

All you need to do is detect modified about:config values and whenever a major problem occurs (e.g. crashes) offer to reset about:config to default.

[opusforlife2]

Wouldn't it be much easier to offer an about:config reset to default on crashes?

Then if the user doesn't have a record of those changed prefs anywhere, they'd have to go back and manually change them again, one by one. A profile backup is a much more elegant solution here. Make a backup before changing a pref -> change a pref -> Fenix crashes -> restore profile backup so you get back to where you were except for that one pref.

[helohe]

@hwinnemoe The worst-case scenario dblohm7 describes is having to reinstall the app, which results in the loss of all open tabs and, if you didn't have sync enabled, all profile data. Coincidentally, that's very similar, although less reversible, to what happens if you switch between release Fenix and beta or nightly, or between release Fenix and F-Droid Fennec. And "use Beta/Nightly instead" is a common Reddit suggestion in response to complaints about Fenix.

Yes that was the same reasoning for me. I needed to switch dns servers and enable esni which is only possible with about config, otherwise I can not access all websites and my custom private lan domains are not resolved. Though first about compiling my own version of FF, but that seems to be too much work. Switched to F-Droid Fennec now and probably wont switch back to FF even if the missing functionality returns.

[caj-larsson]

They weren't disrespectful.

I don't know if you're kidding but to say that the product is "not finished at all" or "Firefox is taking an anti-user, anti-customization stance" is very disrespectful to the developers and not helpful in any way.

It seems true tho. I want to use firefox, but this sledgehammer approach is killing all trust. I've been a proponent since 98 or so, 22 years of support, sharing the tale of Mozilla to the junior developers that never used anything but internet explorer and chrome. Now I feel like a fool.

[omicron-b]

My 2 cents: AFAIK it is impossible to download mp3 file to listen with your own audio player unless you change 'media.play-stand-alone' to 'false'

So, pretty valid use case for a common user.

[cadeyrn]

If that's an important feature for you why not opening a feature request for implementing an option? Since it's the only reason you mention for about:config and you call it a "pretty valid use case for a common user" it seems more useful to advocate for this feature than for about:config, tbh.

[kbrosnan]

Moved to Bugzilla as bz-1813163