Improved about:config Page Makes Editing Hidden Prefs Easier
Monday January 20th, 2003
As many advanced users are aware, Mozilla has lots of 'hidden' preferences that can be tweaked to alter obscure settings or improve performance. Making changes to these prefs used to involve manually editing your prefs.js or user.js file. However, now you can alter these options directly from within the browser, thanks to the fix for bug 107418.
To take advantage of this new feature, you must be running a recent Mozilla or Phoenix nightly. Enter about:config in the Location Bar and a colour-coded list of preferences will appear. Editing them should be familiar to anyone who has ever hacked the Windows Registry: each pref now has a context menu that allows you to copy its name or value to the Clipboard, modify its setting or reset it back to the factory default value. You can also add unlisted preferences by using the 'New' submenu: select 'String' if the value of the setting you want to add is textual, 'Integer' if it's a number or 'Boolean' if it's either
Most modifications will take effect immediately but some may require a restart. Note that making changes in about:config updates prefs.js and not user.js. As the user.js file takes precedence, you'll have to manually remove any lines you want to alter from user.js (or delete the file entirely) before making changes in about:config. Finally, remember that you can really screw things up if you're not careful. You have been warned.
#19 Re: Background colour
Thursday January 23rd, 2003 1:10 AM
You are replying to this message
Same way you've always done UI changes: userChrome.css
Add the following to userChrome.css in your profile (change color to whatever you want)
The main message display, however, is controlled by the mozilla HTML color settings in Edit>Preferences...>Apperance>Colors>Background.
I couldn't tweak the color with the DOM Inspector, which is unusual. If anyone with greater insight can comment, I'd be interested to know why using the DOM Inspector to set background-color on the HTML element (main element in an XUL browser component) doesn't work.