235
edits
(<preferences> need to be last child) |
(clarification) |
||
Line 56: | Line 56: | ||
* The ''id'' of the <prefpane> must be the value of the ''prefpane'' attribute of the <treeitem> (see above). | * The ''id'' of the <prefpane> must be the value of the ''prefpane'' attribute of the <treeitem> (see above). | ||
* The ''label'' should have the same value as the the old <page>.''headertitle'' attribute. It will be shown above the panel. | * The ''label'' should have the same value as the the old <page>.''headertitle'' attribute. It will be shown above the panel. | ||
* The ''script'' attribute contains a whitespace delimited list of chrome URIs of the script files to be loaded into the panel's(!) scope. This means that the contents of these scripts will be accessible as members of the <prefpane> object, eg. ''document.getElementById("navigator_pane"). | * The ''script'' attribute contains a whitespace delimited list of chrome URIs of the script files to be loaded into the panel's(!) scope. This means that the contents of these scripts will (only) be accessible as members of the <prefpane> object, eg. ''document.getElementById("navigator_pane").DoSomething()''. | ||
* The ''onpaneload'' attribute can contain code which will be executed when the panel has finished loading, eg. ''this. | * The ''onpaneload'' attribute can contain code which will be executed when the panel has finished loading, eg. ''this.AfterPrefInit()''. | ||
The old call to ''parent.initPanel'' is not needed anymore, panel initialization is done by the backend. If the panel's loaded scripts contain the special Startup() function, it will be called automatically on panel load. | The old call to ''parent.initPanel'' is not needed anymore, panel initialization is done by the backend. If the panel's loaded scripts contain the special Startup() function, it will be called automatically on panel load. |
edits