Chrome

  • Revision slug: Chrome
  • Revision title: Chrome
  • Revision id: 175845
  • Created:
  • Creator: MarkFinkle
  • Is current revision? No
  • Comment /* See also */

Revision Content

Chrome historically has many meanings in Mozilla.

Browser chrome / Chrome
The "browser chrome" is the UI around the web page, as opposed to the content area.
More generally, chrome is the entirety of entities making up the user interface of a specific application or extension.
A <tt>chrome://</tt> URL
An URL using the <tt>chrome://</tt> protocol. Code loaded from a chrome URL has extended, or chrome, privileges.
XUL-based applications load the code for their interface from <tt>chrome://</tt> URLs.
Chrome privileges
The code running with chrome privileges is allowed to do everything, unlike the web content, which is restricted in several ways.
chrome argument to window.open
Passing the chrome argument to window.open opens a new window without any browser interface elements.
<tt>chrome</tt> folder
This folder is usually a part of a XUL-based application installation. Applications usually load their UI files from the files in this folder.
-chrome command line argument
Starts the application and opens the specified XUL file in a top level window. E.g. mozilla -chrome chrome://inspector/content starts the DOM Inspector.
Chrome package
A chrome package consists of a set of chrome providers. There are three basic types of chrome providers:
  • Content. Content can consist of any file type viewable from within Mozilla. In particular, the content provider most often consists of a set of XUL, JavaScript and XBL binding files.
  • 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.
chrome.rdf
The chrome registry, stores the list of registered chrome packages and other information. It was located in the install directory and in the profile. It is no longer used since Gecko 1.8 (Firefox 1.5).

See also

(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)

{{ languages( { "fr": "fr/Chrome", "ja": "ja/Chrome", "pl": "pl/Chrome" } ) }}

Revision Source

<p>
</p><p><b>Chrome</b> historically has many meanings in Mozilla.
</p>
<dl><dt> Browser chrome / Chrome
</dt><dd> The "browser chrome" is the UI around the web page, as opposed to the content area.
</dd><dd> More generally, chrome is the entirety of entities making up the user interface of a specific application or <a href="en/Extension">extension</a>. </dd><dt> A <tt><a class=" external" href="chrome://" rel="freelink">chrome://</a></tt> URL
</dt><dd> An URL using the <tt><a class=" external" href="chrome://" rel="freelink">chrome://</a></tt> protocol. Code loaded from a chrome URL has extended, or <i>chrome</i>, privileges.
</dd><dd> XUL-based applications load the code for their interface from <tt><a class=" external" href="chrome://" rel="freelink">chrome://</a></tt> URLs.
</dd><dt> Chrome privileges
</dt><dd> The code running with chrome privileges is allowed to do everything, unlike the web content, which is restricted in several ways.
</dd><dt> <code>chrome</code> argument to <code>window.open</code>
</dt><dd> Passing the <a href="en/DOM/window.open#Features_requiring_privileges"><code>chrome</code> argument to <code>window.open</code></a> opens a new window without any browser interface elements.
</dd><dt> <tt>chrome</tt> folder
</dt><dd> This folder is usually a part of a XUL-based application installation. Applications usually load their UI files from the files in this folder.
</dd><dt><code>-chrome</code> command line argument
</dt><dd> Starts the application and opens the specified XUL file in a top level window. E.g. <code>mozilla -chrome <a class=" external" href="chrome://inspector/content" rel="freelink">chrome://inspector/content</a></code> starts the DOM Inspector.
</dd><dt> Chrome package
</dt><dd>A <i>chrome package</i> consists of a set of <i><a href="en/Chrome_Registration">chrome providers</a></i>. There are three basic types of chrome providers:
<ul><li> <b>Content</b>. Content can consist of any file type viewable from within Mozilla. In particular, the content provider most often consists of a set of <a href="en/XUL">XUL</a>, <a href="en/JavaScript">JavaScript</a> and <a href="en/XBL">XBL</a> binding files.
</li><li> <b>Locale</b>. Translations for multi-language support. The two main types of files are <a href="en/XUL_Tutorial/Localization">DTD</a> files and java-style <a href="en/XUL_Tutorial/Property_Files">properties files</a>.
</li><li> <b>Skin</b>. The skin provider provides complete appearance data for the user interface. Consisting of <a href="en/CSS">CSS</a> files and images.
</li></ul>
</dd></dl>
<dl><dt> <code>chrome.rdf</code>
</dt><dd> The chrome registry, stores the list of registered chrome packages and other information. It was located in the install directory and in the profile. It is no longer used since Gecko 1.8 (Firefox 1.5).
</dd></dl>
<h2 id="See_also" name="See_also">See also</h2>
<p>(Note that while both of the documents below mention <tt>contents.rdf</tt> files, an easier way of registering your chrome providers - using <a href="en/Chrome_Registration">Chrome Manifests</a> - is supported since <a href="en/Firefox_1.5">Firefox 1.5</a> / Toolkit 1.8)
</p>
<ul><li> <a href="en/XUL_Tutorial/XUL_Structure">XUL Tutorial:XUL Structure</a>
</li><li> <a href="en/XUL_Tutorial/The_Chrome_URL">XUL_Tutorial:The Chrome URL</a>
</li></ul>
{{ languages( { "fr": "fr/Chrome", "ja": "ja/Chrome", "pl": "pl/Chrome" } ) }}
Revert to this revision