Hello... anybody here? I'm getting disappointed on Mozilla rushing with new versions and not documenting its products. So frustrating!

At the bottom of that page, I found This page was last modified 17:44, 30 May 2015

You can search the Firefox source code on the MXR site if you need documentation of how prefs and CSS code work.

• http://mxr.mozilla.org/

Prefs can change all the time and some prefs only last a few versions or are only used internally (version numbers).

It is impossible to create a documentation that covers every possible aspect of CSS code that you can use in userChrome.css You can use the DOM Inspector to find selectors and check what rules are applied to specific elements.

• DOM Inspector: https://addons.mozilla.org/firefox/addon/dom-inspector-6622/

• https://developer.mozilla.org/DOM_Inspector
• https://developer.mozilla.org/Introduction_to_DOM_Inspector

FredMcD said

At the bottom of that page, I found This page was last modified 17:44, 30 May 2015

It really is not updated much anymore unfortunately as can be seen in http://kb.mozillazine.org/index.php?title=About:config_entries&action=history

But as said some preferences are changed in Options/Preferences panel, some are visible and some are hidden even. Sometimes the preferences in about:config are temporary or version or development channel specific or the default gets changed.

Hidden preferences are often because temporary or risky or testing. You have to add preference type and value manually.

And then there are the loads of preferences added by installed Extensions.

Hello to all

i think, it is interesting the next discussion, please read :Proposal for Firefox about:config article. Any particular reason ...

thank you

cor-el said

You can search the Firefox source code on the MXR site if you need documentation of how prefs and CSS code work.

• http://mxr.mozilla.org/

Prefs can change all the time and some prefs only last a few versions or are only used internally (version numbers). It is impossible to create a documentation that covers every possible aspect of CSS code that you can use in userChrome.css You can use the DOM Inspector to find selectors and check what rules are applied to specific elements.

• DOM Inspector: https://addons.mozilla.org/firefox/addon/dom-inspector-6622/

• https://developer.mozilla.org/DOM_Inspector
• https://developer.mozilla.org/Introduction_to_DOM_Inspector

Thanks for the information. However. I don't have free time to gather technical information from that deep. They really should mantain an updated KB.

Mozilla is really missing the point not listening to it's users needs.

So I was reading this article: http://www.ghacks.net/2015/06/07/mozilla-needs-to-make-up-its-mind/

Note how many features Mozilla released in the last 5 versions of Firefox. How many of those are documented? Where can I disable them? No technical information al all.

It feels like every new version we have a new button in the browser. And thats it? Were is the background? Information for developers?

I think that old saying that "Firefox is customizable" is losing its truth.

"I'd like to see Mozilla change its course again and remove these recently integrated native features from Firefox. The vast majority of Firefox users won't use them and those who do, may as well use them as extensions instead of native code.

These feature additions are controversial and it seems that especially long-time Firefox users are speaking out against their native implementation in the browser." http://www.ghacks.net/2015/06/07/mozilla-needs-to-make-up-its-mind Shout as much as you want Martin... they just won't listen;