Chrome is the entirety of entities making up the user interface of a specific application or extension. Chrome means many things.
The browser UI around the web page.
The chrome protocol which is the only way to get chrome privileges.
A context running with chrome privileges is allowed to do everything.
The directory where applications put their UI files.
-chrome command line argument
Starts and opens a file in a top level window. E.g.
mozilla -chrome chrome://inspector/content starts the DOM Inspector.
chrome argument to
window.open opens a new window without any browser interface elements.
The chrome registry, in the install directory and in the profile.
A chrome package consists of a set of chrome providers. There are three basic types of chrome providers:
- Locale. Translations for multi-language support. The two main types of files are DTD files and java-style properties files.
- Skin. The skin provider provides complete appearance data for the user interface. Consisting of CSS files and images.
(Note that while both of the documents below mention <tt>contents.rdf</tt> files, an easier way of registering your chrome providers - using Chrome Manifests - is supported since Firefox 1.5 / Toolkit 1.8)