mozilla

版本 429719 / Chrome

  • 版本网址缩略名: Chrome
  • 版本标题: Chrome
  • 版本 id: 429719
  • 创建于:
  • 创建者: ziyunfei
  • 是否是当前版本?
  • 评论
标签: 

修订内容

Chrome 这个单词在 Mozilla 的技术中有着多重含义。

Browser chrome / Chrome
"browser chrome" 或者直接 Chrome 可以用来指代围绕着普通网页区域的浏览器界面,它对应的词是 content ,表示网页区域.
更通用点讲, chrome is the entirety of entities making up the user interface of a specific application or extension.
 chrome:// URL
An URL using the chrome:// protocol. Code loaded from a chrome URL has extended, or chrome, privileges.
XUL-based applications load the code for their interface from chrome:// URLs.
Chrome 特权
拥有 chrome 特权的代码可以实现各种事情, 而普通网页中的 JS 代码则不是。
chrome argument to window.open
Passing the chrome argument to window.open opens a new window without any browser interface elements.
chrome 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 contents.rdf 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" } ) }}

修订版来源

<p><b>Chrome</b> 这个单词在 Mozilla 的技术中有着多重含义。</p>
<dl>
  <dt>
    Browser chrome / Chrome</dt>
  <dd>
    "browser chrome" 或者直接 Chrome 可以用来指代围绕着普通网页区域的浏览器界面,它对应的词是 content ,表示网页区域.</dd>
  <dd>
    更通用点讲, chrome is the entirety of entities making up the user interface of a specific application or <a href="en/Extension">extension</a>.</dd>
  <dt>
    &nbsp;<code><a class="external" href="chrome://" rel="freelink">chrome://</a></code> URL</dt>
  <dd>
    An URL using the <code><a class="external" href="chrome://" rel="freelink">chrome://</a></code> 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 <code><a class="external" href="chrome://" rel="freelink">chrome://</a></code> URLs.</dd>
  <dt>
    Chrome 特权</dt>
  <dd>
    拥有 chrome 特权的代码可以实现各种事情, 而普通网页中的 JS 代码则不是。</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>
    <code>chrome</code> 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 <code>contents.rdf</code> 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>
<p>{{ languages( { "fr": "fr/Chrome", "ja": "ja/Chrome", "pl": "pl/Chrome" } ) }}</p>
恢复到这个版本