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

[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