Confirm
1,158
edits
Changes
Created page with "'''Status: draft''' Mozilla has worked with Microsoft and Opera to implemented browser extensions so that developers can write extensions that work across multiple browsers...."
'''Status: draft'''
Mozilla has worked with Microsoft and Opera to implemented browser extensions so that developers can write extensions that work across multiple browsers. The specification matches what Google have implemented in their browser so that extensions work on Chrome.
The [https://browserext.github.io/browserext/ specification can be found on github].
Firefox is in the process of implementing a larger API than has been detailed in the specification. We intend to implement additional APIs in order to differentiate Firefox and empower extension developers.
However, some of those APIs will only be relevant to Firefox because the feature is only available on Firefox. Others might be relevant to other browsers and would be worth submitting to the standard.
As such we can break most parts of the Firefox API down into one of the following categories, a superset of [https://github.com/mdn/browser-compat-data/blob/master/compat-data-schema.md#status-information MDN categories]:
* '''Firefox only''': an API that is unlikely to ever be copied by any other vendor since it is about a Mozilla specific issue or feature. Examples could be the geckoProfiler API or [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextualIdentities contextual identity API].
* '''Experimental''': an API that could be picked up by another vendor and added to the specification. This API might change should that happen. An example could be the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/find/find find API].
* '''Standards-track''': an API that is part of the standards track. Any deviation in Firefox is tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=1392434 bug 1392434].
* '''Deprecated''': this API might be removed and we do not recommend using it. See also [https://wiki.mozilla.org/WebExtensions/DeprecationPolicy draft deprecation plans].
There is a possible progression from “Firefox only” to “Experimental” to the “Standards-track”. For example, the contextual identity API could start as a Firefox only API. It would then be possible for another browser to add in that feature. It could then be moved from Firefox-only over to Experimental in the hopes that we can standardise it.
At this time (October 2017) Firefox implements most of the browser extensions standard across Firefox. Firefox for Android is not as complete. We view that standard as the core of the extensions API for Firefox.
Mozilla has worked with Microsoft and Opera to implemented browser extensions so that developers can write extensions that work across multiple browsers. The specification matches what Google have implemented in their browser so that extensions work on Chrome.
The [https://browserext.github.io/browserext/ specification can be found on github].
Firefox is in the process of implementing a larger API than has been detailed in the specification. We intend to implement additional APIs in order to differentiate Firefox and empower extension developers.
However, some of those APIs will only be relevant to Firefox because the feature is only available on Firefox. Others might be relevant to other browsers and would be worth submitting to the standard.
As such we can break most parts of the Firefox API down into one of the following categories, a superset of [https://github.com/mdn/browser-compat-data/blob/master/compat-data-schema.md#status-information MDN categories]:
* '''Firefox only''': an API that is unlikely to ever be copied by any other vendor since it is about a Mozilla specific issue or feature. Examples could be the geckoProfiler API or [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/contextualIdentities contextual identity API].
* '''Experimental''': an API that could be picked up by another vendor and added to the specification. This API might change should that happen. An example could be the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/find/find find API].
* '''Standards-track''': an API that is part of the standards track. Any deviation in Firefox is tracked in [https://bugzilla.mozilla.org/show_bug.cgi?id=1392434 bug 1392434].
* '''Deprecated''': this API might be removed and we do not recommend using it. See also [https://wiki.mozilla.org/WebExtensions/DeprecationPolicy draft deprecation plans].
There is a possible progression from “Firefox only” to “Experimental” to the “Standards-track”. For example, the contextual identity API could start as a Firefox only API. It would then be possible for another browser to add in that feature. It could then be moved from Firefox-only over to Experimental in the hopes that we can standardise it.
At this time (October 2017) Firefox implements most of the browser extensions standard across Firefox. Firefox for Android is not as complete. We view that standard as the core of the extensions API for Firefox.
