- traditional, requires restart;
- bootstrapped, no restart required;
- within the cloud and JetPack, respectively, possibly bootstrapped, quite over-charged.
One may develop addons very flexibly.
Code-Verification and Messages
saveUri: Messages may be a permanent hint (a bug?); 7 parameters are applied, where the seventh is the required type nsiLoadContext. Though as done as claimed in the documentation, the message appears, however.
- Parameters are constant,
- there are no further options to bind a extern script, and
- message is redundant, since XSS is not supported anymore. See: https://groups.google.com/forum/#!msg/mozilla.dev.extensions/TMFWetkVEDQ/P5RS0liN0A0J.
setting oncommand using setAttribute: may be ignored; this is a dynamically assignment to oncommand, this is
- a statically assignemnt,
- due to the handler's concept, this is required, as oncommand is applied by system-wide shortcuts first. So, there is no further possibility to set shortcuts.
Verifications' Do-it-your-self Tests
Addon development is divided:
- popup.js: contains the pop-up's script, active only as long as the pop-up is open.
- popup.html: contains the pop-up's UI.
- background.js: the script that runs in the background.
- content.js: a script to be injected into a running document.
Microsoft only supports the development of add-ons using C# or C++, respectively, through so-called Browser Helper Objects (status-quo of IE9) -- a typical DLL containing SHDocVw-Binding for C++ and C#.