Add-ons/developer/communication

From MozillaWiki
< Add-ons
Revision as of 20:31, 30 September 2016 by AmyT (talk | contribs) (new blog posts)
Jump to navigation Jump to search

Evolution in Add-on Development

WebExtensions are becoming the standard for add-on development in Firefox. At the same time, multiprocess Firefox (aka Electrolysis, or e10s) is also rolling out. These changes impact developers of XUL/XPCOM and SDK add-ons (some more than others), so we've created resources here to help ease the transitions.

This page contains timelines, migration paths, tutorials, and more. If you're a new developer and would like create an add-on, please head over to MDN.

Find out if you are affected
What's New

Timelines & Roadmap

Migration paths for developers affected by the changes

1) Has SDK add-on using low level APIs

Developers who created an SDK add-on using low-level APIs, which break with Multi-process Firefox (aka Electrolysis or e10s).

Migration Path

If your add-on code accesses web content using a low-level SDK APIs like window/utils or tabs/utils, then you will likely be affected.
Multi-process Firefox is currently going through a phased roll-out few months, so we urge you to test your add-ons for compatibility.

  • If it breaks in Multi-process Firefox, your users will be impacted, and you will need to update your add-on. You can find documentation on how to make them compatible here.
  • If it does not break in Multi-process Firefox, you will should add the multiprocess permission in package.json.

There are people on hand to assist you every Tuesday in the #addons channel at irc.mozilla.org. We're here to help!

~~Attention SDK developers~~
As of March 2016, SDK add-ons that were built using the cfx tool (Jetpack version 1.17 and lower) need to be repackaged using the newer jpm tool in order to continue being compatible with Firefox. jpm will be supported for as long as the SDK is.

2) Has SDK add-on using legacy APIs

Developers who created an SDK add-on, but uses either XPCOM or other legacy APIs.

Migration Path

Developers in this group potentially have to update their add-on twice--once for e10s compatibility (if using low-level APIs), and again for WebExtensions compatibility (because it uses legacy APIs).

  1. Use only high-level APIs - High-level APIs are e10s compatible and are more likely to have an equivalent WebExtensions API. You will have to migrate again once WebExtensions are fully ready, but it should be pretty easy to do in this case.
  2. Move to WebExtensions - Check the SDK/WebExtensions comparison chart to see if the APIs you need are available, and see what else we're doing to mitigate the impact of this transition. If you have a WebExtensions API you'd like to see implemented, file them here.

3) Has SDK add-on using only high level APIs

Developers who used the SDK for their add-ons using only high-level APIs. Might have played around with the Chrome extension API in the past.

Migration Path
  • As of March 2016, SDK add-ons that were built using the cfx tool (Jetpack version 1.17 and lower) need to be repackaged using the newer jpm tool in order to continue being compatible with Firefox.
  • If you already do that, your add-on will probably continue to work without problems, but we recommend you start looking into WebExtensions.
  • Check the SDK/WebExtensions comparison chart to see if the APIs you need are available, and see what else we're doing to mitigate the impact of this transition. If you have a WebExtensions API you'd like to see implemented, file them here.

4) Has XUL or XPCOM add-on

Developers who created add-ons that don't rely on the SDK or WebExtensions.

Migration Path

The transition to WebExtensions impacts add-ons built on APIs like XUL and XPCOM most of all. We expect to remove support for these technologies in Firefox add-ons by the end of 2017. We hope this will give us enough time to help you migrate and provide WebExtension APIs that are suitable for replacing the features you might lose once we stop supporting these APIs.

If you’ve already updated your add-on for Multiprocess Firefox (e10s) compatibility, thank you for clearing this hurdle. To prepare for XUL/XPCOM deprecation, there are two available options, each with pros and cons:

  1. Migrate to the Add-ons SDK - since WebExtensions is in development and the first release is scheduled for March 2016, one option you have is to migrate to the SDK.
    • Pros: the APIs provided by the SDK are well-documented and are fully functional. Migrating to WebExtensions later on will be easier.
    • Cons: you will need to to stick to high-level APIs, which are e10s compatible and are more likely to have an equivalent WebExtensions API. You will have to migrate again once WebExtensions are fully ready, though it may be easier if you’ve already migrated to the SDK. Check the SDK/WebExtensions comparison chart to see if the APIs you need are available. If you have a WebExtensions API you'd like to see implemented, file them here.
  2. Migrate to WebExtensions - to avoid having to migrate to SDK and then again to WebExtensions, you can migrate directly to WebExtensions.

Managing the Impact

  • Embedded WebExtensions - In Firefox 51, you can embed a WebExtensions add-on inside an existing SDK or bootstrapped add-on. This is especially useful to developers of SDK or bootstrapped add-ons who want to start migrating to WebExtensions and take advantage of new APIs like Native Messaging, but can’t fully migrate yet. It’s also useful for developers who want to complete data migration towards WebExtensions, and who want to take parts of their add-on that are not compatible with multiprocess Firefox and make them compatible.
  • Tell us which APIs you need - If you have a WebExtensions API you'd like to see implemented, take a look at the new APIs criteria.

It is possible that not all add-ons will be able to migrate to WebExtensions without having to drop any features. But we want to work with you to get as many add-ons migrated as possible with the functionality you created intact. We invite you to contribute to its evolution, and we look forward to working with you.

Add-on Developer Communication Calendar

This calendar includes public meetings, scheduled blog posts, office hours, release milestones that affect add-on developers, and more. Links to add it to your own calendar: iCal | HTML

Error in widget Widget:Google Calendar: Unable to load template 'wiki:Widget:Google Calendar'

Blog Posts and Other Resources

WebExtensions

Blog Posts
Other Resources

Multiprocess (e10s) Firefox

Blog Posts
Other Resources

Migrating from XUL/XPCOM

Blog Posts
Other Resources

Get in Touch

  • IRC:
    • #teamaddons: team chat
    • #addons: support for extensions, themes, plugins and addons.mozilla.org
    • #amo: addons.mozilla.org bugs and development
    • #amo-editors: add-on reviews and policy
    • #extdev: extension development
    • #themedev: theme development
    • #webextensions: web extensions
Retrieved from "https://wiki.mozilla.org/index.php?title=Add-ons/developer/communication&oldid=1149816"