Revision 925949 of chrome

<p><span class="seoSummary">The chrome module is the only way to access chrome functionality using the Add-on SDK.</span></p>

<div class="warning">
<p class="bz_comment_text" id="comment_text_2">You should avoid using the API if it's at all possible. We intend to deprecate it in future releases. Its use currently causes an extra add-on security review.</p>
</div>

<p class="bz_comment_text" id="comment_text_2">The chrome module gives an Add-on SDK add-on access to the Components object, which in turn gives it access to a large set of privileged low-level APIs.</p>

<p>chome is a built-in pseudo module of the toolkit <a href="/en-US/Add-ons/SDK/Low-Level_APIs/_loader#chrome">loader</a>. See the <a href="/en-US/Add-ons/SDK/Tutorials/Chrome_Authority">chrome authority</a> tutorial for more details.</p>

<p class="bz_comment_text" id="comment_text_2">An example of this API's use is availabe in the <a href="/en-US/Add-ons/SDK/Guides/XUL_Migration_Guide#Using_XPCOM">XUL Migration Guide</a>.</p>

<div class="warning">
<p>This module is not to be confused with the "chrome" global variable that <a href="https://wiki.mozilla.org/WebExtensions#Namespacing">WebExtensions</a> can use to access APIs.</p>
</div>