Confirmed users
130
edits
WebExtensions: Difference between revisions
Jump to navigation
Jump to search
more packaging details
Wmccloskey (talk | contribs) (packaging) |
Wmccloskey (talk | contribs) (more packaging details) |
||
| Line 1: | Line 1: | ||
This page is an introduction to Mozilla's implementation of a new browser extension API. The goals of this API are: | This page is an introduction to Mozilla's implementation of WebExtensions, a new browser extension API. The goals of this API are: | ||
* It should be easier to use. | * It should be easier to use. | ||
* It must be compatible with multiprocess Firefox ([[Electrolysis]]). | * It must be compatible with multiprocess Firefox ([[Electrolysis]]). | ||
| Line 12: | Line 12: | ||
== Packaging == | == Packaging == | ||
At this point it's difficult to experiment with the API because extensions cannot be installed directly. [https://bugzilla.mozilla.org/show_bug.cgi?id=1190692 Bug 1190692] tracks the work to make it possible to install them using the add-on manager. The only way WebExtensions can be installed right now is to package them into XPIs via [http://mxr.mozilla.org/mozilla-central/source/browser/components/extensions/prepare.py a Python script]. This script generates install.rdf and bootstrap.js files. It can then be zipped into an .xpi and installed using the add-on manager. | |||
In the future, we're planning to use the .zip file extension. All of the data currently in install.rdf will be moved to the manifest.json file. Will will not use install.rdf or bootstrap.js. Extensions will be signed using JAR signing (the same as we do for existing Firefox add-ons). | |||
See https://developer.chrome.com/extensions/manifest for a complete list of manifest directives. The ones we currently support are below. | See https://developer.chrome.com/extensions/manifest for a complete list of manifest directives. The ones we currently support are below. | ||