Confirm
1,605
edits
Changes
m
link to WE suggestion prompt
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_legacy_Firefox_add-on Porting guides that map SDK and XUL APIs to available WebExtensions APIs]
*[https://developer.mozilla.org/en-US/Add-ons/WebExtensions How-to guides] covering common add-on developer cases, like [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Intercept_HTTP_requests intercepting web requests] and [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Add_a_button_to_the_toolbar adding a button to the toolbar]
*If you have a WebExtensions API you'd like to see implemented, [https://wiki.mozilla.org/WebExtensions/NewAPIs#Submitting_an_API.3F file them here].
=Timelines & Roadmap=
#'''Use only [https://developer.mozilla.org/Add-ons/SDK/High-Level_APIs high-level APIs]''' - High-level APIs are [https://wiki.mozilla.org/Add-ons/developer/communication#1.29_Has_SDK_add-on_using_low_level_APIs 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.
#'''Move to [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions WebExtensions]''' - Check the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK SDK/WebExtensions comparison chart] to see if the APIs you need are available, and see what else we're doing to [[Add-ons/developer/communication#Managing_the_Impact|mitigate the impact]] of this transition. If you have a WebExtensions API you'd like to see implemented, [https://wiki.mozilla.org/WebExtensions/NewAPIs#Submitting_an_API.3F file them here].
==3) Has SDK add-on using only high level APIs==
*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 [https://developer.mozilla.org/Add-ons/SDK/Tools/cfx_to_jpm 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 [https://developer.mozilla.org/Add-ons/WebExtensions WebExtensions].
*Check the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK SDK/WebExtensions comparison chart] to see if the APIs you need are available, and see what else we're doing to [[Add-ons/developer/communication#Managing_the_Impact|mitigate the impact]] of this transition. If you have a WebExtensions API you'd like to see implemented, [https://wiki.mozilla.org/WebExtensions/NewAPIs#Submitting_an_API.3F file them here].
==4) Has XUL or XPCOM add-on==
<ol><li>'''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 [https://developer.mozilla.org/en-US/Add-ons/SDK 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 [https://developer.mozilla.org/Add-ons/SDK/High-Level_APIs 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 [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK 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, [https://wiki.mozilla.org/WebExtensions/NewAPIs#Submitting_an_API.3F file them here].</li>
<li>'''Migrate to WebExtensions''' - to avoid having to migrate to SDK and then again to WebExtensions, you can [https://developer.mozilla.org/Add-ons/WebExtensions migrate directly to WebExtensions].
*'''Pros:''' you only have to migrate once.
*'''Cons:''' WebExtensions may not have all the APIs you need. Check the [https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Comparison_with_XUL_XPCOM_extensions XUL/XPCOM-WebExtensions comparison chart] to see if the APIs you need are available, and see what else we're doing to [[Add-ons/developer/communication#Managing_the_Impact|mitigate the impact]] of this transition. If you have a WebExtensions API you'd like to see implemented, [https://wiki.mozilla.org/WebExtensions/NewAPIs#Submitting_an_API.3F file them here].
</li>
</ol>
=Managing the Impact=
*'''Tell us which APIs you need''' - Please use the following channels to tell us which APIs If you need in have a WebExtensions. This will help us prioritize and plan for what we need API you'd like to support.**Join the mailing list at see implemented, [https://mailwiki.mozilla.org/listinfoWebExtensions/dev-addons dev-addons@mozillaNewAPIs#Submitting_an_API.org3F file them here].**Join us on [[IRC|IRC]] at #webextensions or #addons
*'''WebExtensions Experiments (formerly Native.js)''' - We want to give developers a way to develop and experiment with APIs that go beyond what Chrome provides. To get involved, read about the project [https://wiki.mozilla.org/WebExtensions/Experiments here] and the corresponding [https://wiki.mozilla.org/WebExtensions/NewAPIs criteria] for evaluating new APIs.
