Firefox/AddOns/Status/current: Difference between revisions

Line 262: Line 262:
=<big>'''Add-ons WebExtensions Status Report'''</big>=
=<big>'''Add-ons WebExtensions Status Report'''</big>=
Here is the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK current list of how WebExtensions correlate to the JetPack SDK] and links to documentation.  The idea is if something is developed for Chrome it will take no to minimal effort to move to Firefox.  Microsoft Edge and Safari are also adopting this model.  WebExtensions are being built multi-process (e10s) compliant.  Whenever possible we are focusing on creating WebExtensions APIs first that also assist the most Firefox add-ons with upgrading to multi-process compatibility.
Here is the [https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Comparison_with_the_Add-on_SDK current list of how WebExtensions correlate to the JetPack SDK] and links to documentation.  The idea is if something is developed for Chrome it will take no to minimal effort to move to Firefox.  Microsoft Edge and Safari are also adopting this model.  WebExtensions are being built multi-process (e10s) compliant.  Whenever possible we are focusing on creating WebExtensions APIs first that also assist the most Firefox add-ons with upgrading to multi-process compatibility.
== Exec Summary/Hot Topics - Nov 1, 2016 ==
== Exec Summary/Hot Topics - Nov 30, 2016 ==
*WebExtensions has been the [http://bit.ly/2e7dp8j most popular platform for new add-ons since July]  
*WebExtensions has been the [http://bit.ly/2e7dp8j most popular platform for new add-ons since July]  
*Communication coming end of November for 2017 plans and updates around add-on development platform
*Communication coming end of November for 2017 plans and updates around add-on development platform
Confirmed users
1,094

edits