I would personally like to see that be a WebExtension. Will an extension like Tree Style Tab be possible to convert to a WebExension? Something tells me it wont, and that scares the hell out of me. We hope to bring more APIs to the browser than Chrome does and you can see some of those in the bugs. What does chrome support that Web Extensions will not support (the “Not Likely” tags on arewewebextensionsyet perhaps?) and what special features or APIs does Web Extensions bring (Access to toolbars or downloads or something? tab behavior modification? etc?) While it’d be helpful for me to see API differences, at this point I’m mostly interested in vague feature differences. Is there a place to see the differences between the Chrome extensions APIs and Web Extensions? I wanted to advertise a tool to analyse/convert chrome extensions: ĭisclosure: I have contributed some commits there during the past few days. If you’d like to jump in to help, or get your API added, then please join us on our mailing list or at one of our public meetings.Ĭategories: developers, webextensions 17 responses Over the coming months we will work our way towards a beta in Firefox 47 and the first stable release in Firefox 48. Documentation is being worked on in MDN and a set of example WebExtensions is available. All add-ons built with WebExtensions are fully compatible with a multiprocess Firefox and will work in Chrome and Opera.īeyond APIs, support is being added to to enable developers to upload their add-ons and have them tested, that should be ready for Firefox 44.
How to use extensions in firefox version 45 full#
Plus a bunch of partially supported APIs: bookmarks, cookies, extension, i18n, notifications, runtime, storage, tabs, webNavigation, webRequest, windows.Ī full list of the API differences is available, and you can also follow along on the state of WebExtensions on. With the release of Firefox 45 in March 2016, we’ll have full support for the following APIs: alarms, contextMenus, pageAction and browserAction. Since August, we’ve closed 77 bugs and ramped up the WebExtensions team at Mozilla. WebExtensions is currently in an alpha state, so while this is a great time to get involved, please keep in mind that things might change if you decide to use it in its current state. This post covers the progress we’ve made since then. In August we announced that work had begun on the WebExtensions API as the future of developing add-ons in Firefox.