Learn the first steps required to modify Firefox without using formal release processes.
At the base of Firefox is an efficient and unchangeable runtime engine. On top of that is a thick layer of interpreted content. That thick layer of content is human-readable and human-changeable. This hack describes how to find, open, and modify these files without getting burnt and without preparing an extension.
Files centrally associated with the chrome are found in the Firefox install area. Because these central chrome files aren't implemented as extensions, the -safe-mode command-line option [Hack #10] doesn't apply. If you damage chrome files, there is no way to successfully restart Firefox without repair or reinstall. You've been warned.
First, the chrome is a little database of information held in Firefox's memory. This database is created at startup time from many separate RDF files. Only those pieces of user interface that are known to this database are considered chrome. RDF package registration is required to make a package known. You can't place a file in the Firefox install area and expect it to be treated as chrome unless it is part ...