-
Notifications
You must be signed in to change notification settings - Fork 1.3k
about:config doesn't work in Firefox Release #7865
Comments
I would also like Also, So I would consider |
I found bz#1540065 from a year ago that says:
So it sounds like it should be available on all release branches including stable. |
We currently have it enabled in Nightly. Keeping this open as something to consider in the future |
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. |
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. |
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. |
It's time to enable about:config on all versions. |
I created enhancement request on Bugzilla for GeckoView to display warning when opening Also, can we get any confirmation from devs if they would consider enabling (and then enable) |
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. |
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. |
I'd like to configure |
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. |
###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.
It also needs constraints on what values you can use
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.
And finally, some things should simply be deprecated, locked, or hidden as configurable.
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.) |
The socks proxy feature is important in the about:config settings. So please do have a quick release:) |
Anyway, why is Mozilla releasing an actually beta release which is not finished and advertized as 'official' and 'customizable' ? And here I repeat the text of [mcl21014] which I got in my mail and I fully agree, but is probably modded away.
|
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 :) 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. |
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. |
Is there ever made a poll ?
These addons and about:config are not so specific as Mozilla thinks. And a FF with all add-ons and about:config still works for the regular user who don't use this. 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. |
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 |
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. |
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/ |
"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. "klint" commented: where he admits that the product is not finished yet. |
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. |
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. |
Okay, this really needs to be part of official Mozilla merch. Mozilla, please sell Firefox nighties! :P |
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... |
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. |
@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. |
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. |
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. |
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. |
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. |
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. |
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. |
Moved to Bugzilla as bz-1813163 |
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
The text was updated successfully, but these errors were encountered: