Confirmed users
1,605
edits
Firefox/AddOns/Status/current: Difference between revisions
m
→Add-ons WebExtensions Status Report: WebExtensions nit
m (→Add-ons Webextensions Status Report: WebExtensions) |
m (→Add-ons WebExtensions Status Report: WebExtensions nit) |
||
| Line 258: | Line 258: | ||
=<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 | 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 working to adopt 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 - Oct 10th, 2016 == | == Exec Summary/Hot Topics - Oct 10th, 2016 == | ||
<!--Should explain WHY for the health/status reported below. Items covered here may be covered in more detail further down in the report. If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.--> | <!--Should explain WHY for the health/status reported below. Items covered here may be covered in more detail further down in the report. If senior management were to look at nothing but this section, they should be able to tell what is going on with the project.--> | ||