If you are looking for documentation on how to develop an extension with WebExtensions APIs with Firefox,. This page is an introduction to Mozilla's implementation of WebExtensions, a new browser extension API; a cross-browser system for developing extensions. The goals of this API are: • Porting add-ons to and from other browsers should be easier. • Reviewing add-ons for addons.mozilla.org (AMO) should be easier. • Compatibility with multiprocess Firefox (). • Changes to Firefox's internal code should be less likely to break add-ons.
• WebExtensions APIs should be easier to use than the existing Firefox XPCOM/XUL APIs. • WebExtensions APIs should maintain acceptable security and privacy standards. Much of the specifics of the new API are similar to the Blink extension API. But the are the best. Please note: the API is called 'WebExtensions' because it can be found in search engines; 'Web Extensions' (with a space) does not yield relevant results.
Information on terminology usage is available. Contents • • • • • • • • • • • • • Status • Bugs are filed in Bugzilla under WebExtensions, Useful queries • • • (note: this is different from the untriaged component) • • • • Firefox 57 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 is a publicly available as part of.