mozilla

Revision 175843 of Chrome

  • Revision slug: Chrome
  • Revision title: Chrome
  • Revision id: 175843
  • Created:
  • Creator: Andreas Wuest
  • Is current revision? No
  • Comment Extended as proposed on the talk page.

Revision Content

Chrome is the entirety of entities making up the user interface of a specific application or extension. Chrome means many things.

Browser chrome

The browser UI around the web page.

Chrome URL

The chrome protocol which is the only way to get chrome privileges.

Chrome privileges

A context running with chrome privileges is allowed to do everything.

Chrome directory

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

Passing the chrome argument to window.open opens a new window without any browser interface elements.

chrome.rdf

The chrome registry, in the install directory and in the profile.

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.

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)

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

Revision Source

<p>
</p><p><b>Chrome</b> is the entirety of entities making up the user interface of a specific application or <a href="en/Extension">extension</a>. <i>Chrome</i> means many things.
</p>
<h2 name="Browser_chrome">Browser chrome</h2>
<p>The browser UI around the web page.
</p>
<h2 name="Chrome_URL">Chrome URL</h2>
<p>The chrome protocol which is the only way to get chrome privileges.
</p>
<h2 name="Chrome_privileges">Chrome privileges</h2>
<p>A context running with chrome privileges is allowed to do everything.
</p>
<h2 name="Chrome_directory">Chrome directory</h2>
<p>The directory where applications put their UI files.
</p>
<h2 name="-chrome_command_line_argument"><code>-chrome</code> command line argument</h2>
<p>Starts and opens a file in a top level window. E.g. <code>mozilla -chrome chrome://inspector/content</code> starts the DOM Inspector.
</p>
<h2 name="chrome_argument"><code>chrome</code> argument</h2>
<p>Passing the <a href="en/DOM/window.open#Features_requiring_privileges"><code>chrome</code> argument</a> to <code>window.open</code> opens a new window without any browser interface elements.
</p>
<h2 name="chrome.rdf"><code>chrome.rdf</code></h2>
<p>The chrome registry, in the install directory and in the profile.
</p>
<h2 name="Chrome_package">Chrome package</h2>
<p>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:
</p>
<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>
<h2 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 class="external" href="http://xulplanet.com/tutorials/xultu/chromeurl.html">The Chrome URL</a>
</li></ul>
{{ wiki.languages( { "fr": "fr/Chrome", "ja": "ja/Chrome", "pl": "pl/Chrome" } ) }}
Revert to this revision