MozillaZine

Editing configuration

From MozillaZine Knowledge Base

(Difference between revisions)
Revision as of 16:47, 4 January 2006
Mozcerize (Talk | contribs)
(added more info, tidied up)
<-- Previous diff
Revision as of 16:57, 4 January 2006
Mozcerize (Talk | contribs)
(reordering the material)
Next diff -->
Line 1: Line 1:
-Mozilla applications are highly customizable, and there are a number of standard ways to change their appearance and behaviour. Basic settings can be changed using the application's dialog boxes. The main Options or Preferences dialogs can be reached from the "Tools" or "Edit" menus. (See [[menu differences in Windows, Linux, and Mac]].)+Mozilla applications are highly customizable, and there are a number of standard ways to change their appearance and behaviour.
-[https://addons.mozilla.org Extensions and themes] provide many additional features and allow you to change the way your application looks.+==Modifying preferences==
 +Basic settings can be changed using the application's dialog boxes. The main Options or Preferences dialogs can be reached from the "Tools" or "Edit" menus. (See [[menu differences in Windows, Linux, and Mac]].)
-For more advanced configuration, you should use one of the methods below. (The [https://addons.mozilla.org/extensions/moreinfo.php?id=17 ChromEdit] extension provides a convenient way of editing the configuration files described below. Note that version 0.1.1.1 is not compatible with Thunderbird 1.0.2.)+To make more advanced changes to the application&rsquo;s behaviour, you should either edit the [[user.js file]], or use the [[about:config]] interface. Note that whilst it is often quicker to use about:config, editing the "user.js" file has the advantage of portability: your settings will never be overridden, and they can be transferred to a different profile, or backed up for safe keeping.
-To modify the way in which Web pages are displayed, you should edit the [[userChrome.css and userContent.css | userContent.css]] file.+==Modifying appearance==
- +To modify the way in which Web pages are displayed, you should edit the [[userChrome.css and userContent.css | userContent.css]] file. To modify the appearance of the application itself, you should edit the [[userChrome.css and userContent.css | userChrome.css]] file.
-To modify the appearance of the application itself, you should edit the [[userChrome.css and userContent.css | userChrome.css]] file.+
- +
-To make changes to the application&rsquo;s behaviour, you should either edit the [[user.js file]], or use the [[about:config]] interface. Note that whilst it is often quicker to use about:config, editing the "user.js" file has the advantage of portability: your settings can be transferred to a different profile, or backed up for safe keeping.+
==External links== ==External links==
 +* The [https://addons.mozilla.org/extensions/moreinfo.php?id=17 ChromEdit] extension provides a convenient way of editing the configuration files described below. Note that version 0.1.1.1 is not compatible with Thunderbird 1.0.2.)
 +* [https://addons.mozilla.org Extensions and themes] provide many additional features and allow you to change the way your application looks.
* [http://www.mozilla.org/support/firefox/edit Editing Configuration Files] at Firefox Help * [http://www.mozilla.org/support/firefox/edit Editing Configuration Files] at Firefox Help
* [http://www.mozilla.org/support/thunderbird/edit Editing Configuration Files] at Thunderbird Help * [http://www.mozilla.org/support/thunderbird/edit Editing Configuration Files] at Thunderbird Help
[[Category:Configuration]] [[Category:Configuration]]

Revision as of 16:57, 4 January 2006

Mozilla applications are highly customizable, and there are a number of standard ways to change their appearance and behaviour.

Modifying preferences

Basic settings can be changed using the application's dialog boxes. The main Options or Preferences dialogs can be reached from the "Tools" or "Edit" menus. (See menu differences in Windows, Linux, and Mac.)

To make more advanced changes to the application’s behaviour, you should either edit the user.js file, or use the about:config interface. Note that whilst it is often quicker to use about:config, editing the "user.js" file has the advantage of portability: your settings will never be overridden, and they can be transferred to a different profile, or backed up for safe keeping.

Modifying appearance

To modify the way in which Web pages are displayed, you should edit the userContent.css file. To modify the appearance of the application itself, you should edit the userChrome.css file.

External links