oasisjas.blogg.se

This process is performed by jpm xpi resulting in a packed. Without this process, Firefox will not be able to load the add-on. This process wraps the Add-on SDK extension into a Bootstrap/Restartless add-on, which is understood by Firefox. The files which are typically edited for an Add-on SDK extension do not make a complete extension without some additional wrapping functions and the package.json file being translated into an install.rdf file and, possibly, a chrome.manifest file. In general, you will use jpm run to test your Firefox Add-on SDK extension. You can not load a Firefox Add-on SDK extension as a temporary add-on without first packaging it into an. This can be done with the add-on files either unpacked, or packaged in an. WebExtensions can be loaded as Temporary Add-ons. Mozilla documentation: Temporary Installation in Firefox WebExtensions

Temporary Add-on remain installed until manually uninstalled, or Firefox restarts. Temporary Add-ons do not need to be signed. xpi file), or an add-on which is packed into an.

The following animation shows loading an add-on named "aaaaaaaaaaaaaaaaaa - demo add-on" from about:debugging and that the add-on then shows up in about:addons:Īs a Temporary Add-on, you can load either an unpacked add-on (a directory which contains all files for the add-on which you would pack into an. In the file picker, navigate to the directory containing the add-on files.You can do so by loading it as a Temporary Add-on. To test an add-on you are developing, you will likely desire to install it in Firefox temporarily.