This page is an introduction to Mozilla's implementation of WebExtensions, a new browser extension API. The goals of this API are:
- Porting add-ons to and from other browsers should be easier.
- Reviewing add-ons for addons.mozilla.org should be easier.
- WebExtensions must be compatible with multiprocess Firefox (Electrolysis).
- Changes to Firefox's internal code should be less likely to break add-ons.
- WebExtensions should be easier to use than the existing Firefox XPCOM/XUL APIs.
- WebExtensions should maintain acceptable security and privacy standards.
Please note: we are going with the name WebExtensions because it can be used in search engines, not Web Extensions (with a space) which is almost impossible to search.
- Bugs are filed in Bugzilla under Toolkit > WebExtensions, find or create a bug
- Need documentation
- Untriaged (note: this is different from the untriaged component)
- Design Decision Needed
- Advisory Group
- All bugs
- Closed in past 17 days
To keep track of priorities for Firefox 57, we are using the webextensions tracking flag. You can nominate a bug by using the flag with a ?. Bugs that are not on the tracking flag may still be worked but, but will not be a priority. All bugs must have a priority and preferably an assignee. All P1 bugs must have an assignee.
Communication and meetings
- There are developer resources to help you through the migration.
- Currently every week there is a public triage meeting of the bugs we hope to complete.
- Every other week there is a triage of WebExtensions APIs.
- Join the mailing list at firstname.lastname@example.org.
- Join us on IRC at #webextensions or #addons
Testing out the WebExtensions API
See Your first WebExtension on MDN.
At this time, all APIs are accessible through the chrome.* and browser.* namespace. When we begin to add our own APIs, we expect to add them to the browser.* namespace.
WebExtensions are compatible with Electrolysis. They run in the main Firefox process (except for content scripts, which run in the same process as web content). We are considering a plan to run extensions in a separate process (or possibly the content process) eventually, see 1190679 for more details.
Technical details about the implementation are published at WebExtensions/Implementing_APIs_out-of-process.
Extensions are packaged as standard Zip files, but with
.xpi extensions. In the future, we're planning to move towards whatever the W3C WG recommends.
See https://developer.chrome.com/extensions/manifest for a complete list of manifest directives.
API support status
The list of APIs and their status is now maintained on MDN. We intend to fix any of the exceptions listed there.
Please also see arewewebextensionsyet.com for an up to date list of supported APIs that is taken by parsing schemas defined in mozilla-central. No guarantees are made on this site, the MDN page is definitive in case of disagreement.
- If you're experienced with Mozilla infrastructure and would like to develop WebExtensions APIs directly for Firefox, here is a list of approved APIs that you can start contributing to.
- If you'd like to become familiar with Mozilla infrastructure so you can develop WebExtensions APIs directly for Firefox, follow these steps:
- If you just want to tinker with WebExtensions APIs without having to build Firefox, WebExtensions Experiments is for you!
- If you simply want to request a WebExtensions API, please file a bug. These are triaged and processed in a bi-weekly public meeting.
Please see the hacking guide for information about contributing code to the WebExtensions project.
Please see https://webextensions-experiments.readthedocs.io/en/latest/ for some information on Experiments which might be useful for contributing.
Here is a list of all add-on contribution opportunities.