# W3C and WebExtensions APIs

**URL:** <https://discourse.mozilla.org/t/w3c-and-webextensions-apis/20421>\
**Category:** Announcements\
**Created:** [October 13, 2017, 7:52pm UTC](https://discourse.mozilla.org/t/w3c-and-webextensions-apis/20421 "2017-10-13T19:52:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![caitlin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/caitlin/32/6091_2.png) [@caitlin](https://discourse.mozilla.org/u/caitlin)\
**Post date:** [October 13, 2017, 7:52pm UTC](https://discourse.mozilla.org/t/w3c-and-webextensions-apis/20421/1 "2017-10-13T19:52:13Z")

</div>

We’ve been working on getting WebExtensions ready for Firefox 57, and  
wanted to follow up with our status regarding the [W3C Community Group](https://www.w3.org/community/browserext/).

At this time Firefox implements a large part of the specification.  
Deviations from the spec are being tracked in [bug 1392434](https://bugzilla.mozilla.org/show_bug.cgi?id=1392434).  
Following the specification allows developers to write extensions and  
know that the core of the extension will work across browsers, and  
also understand where browsers may diverge from the specification.

We believe that extensions can do more than they do today, and will  
continue to expand the API set Firefox supports as we move forward. As  
we extend the APIs available to developers, we’ll be marking the API  
appropriately on [MDN](https://bugzilla.mozilla.org/show_bug.cgi?id=1408494) so developers know what to expect. It is our  
hope that other browsers will do the same, and that we’ll collectively  
grow the extension API.

This is documented on the [wiki](https://wiki.mozilla.org/WebExtensions/Spec).

_You can read the original email about this topic on the [dev-addons archive](https://mail.mozilla.org/pipermail/dev-addons/2017-October/003272.html)._