* They have the ability to register callbacks that perform cleanup tasks when unloaded.
* They have full access to XPConnect's <tt>Components</tt> object, and all its sub-objects.
* When used in a XULRunner extension, they the Chrome Booster framework should have the following additional characteristics: * Adding Chrome Booster functionality to an existing XULRunner extension should be as painless as possible; ideally, it should consist merely of adding a single script, <tt>booster.js</tt>, and any desired SecurableModule files.* Using <tt>booster.js</tt> should be equally at home just as easy in both a chrome-privileged page/window and a JS module.
For security purposes, Chrome Boosters can only be accessed either
