December 8, 2000


Digital Photography






Web Page Design

Web Tools

Step 2. Preparing to edit the installed-chrome.txt file

a). Open the installed-chrome.txt file for editing (use any text editor such as NotePad in Windows and pico or vi in any Linux or *NIX system). You should see about 30 to 40 or so lines of code.

b). Please notice that most of the installed-chrome.txt lines have the one of these general forms:

content,install,url,jar:resource:/chrome/comm.jar!/ content/necko/

locale,install,url,jar:resource:/chrome/en-US.jar!/locale/ en-US/navigator/

skin,install,url,jar:resource:/chrome/classic.jar!/skin/ classic/navigator/

These lines direct mozilla to get UI layout information from the designated .jar file instead of from the un-jarred chrome and skin files

Getting to the point, you made changes to the XUL, DTD, or other chrome and skin files -- yet nothing changed in the way your Mozilla browser or application skin is displayed. That's because your installed-chrome.txt file points to the jar archives, not to the directory where you modified the files.

However, while we are customizing the chrome and skins we do not want Mozilla to look for the user interface (UI) information in the jar archives. Our goal here is to point installed-chrome.txt to the modified chrome and skin directories, not to the JAR files.

If we remove the references to jar: and .jar! in the installed-chrome.txt file, then Mozilla will not look to the JAR files for chrome and skin information. Mozilla will look to the chrome and skin directories you have modified for display information and paint the browser face or application desktop, the UI, that you have defined by modifying the chrome and skin files.

Related Stories

Article Index

Page 1
About JARs
Page 2


Page 3

File Editing, Finish, & Resources

Recent Articles

Upcoming Articles

Copyright 2000 -- MozillaQuest -- Brodheadsville, Pa..USA -- All Rights Reserved