Confirmed users
1,158
edits
WebExtensions/Roadmap: Difference between revisions
no edit summary
(Created page with "This is an initial roadmap of WebExtensions.") |
No edit summary |
||
| Line 1: | Line 1: | ||
This is an initial roadmap of WebExtensions. | This is an initial roadmap of WebExtensions. | ||
Status: '''draft, in progress'''. | |||
WebExtensions exist at the time of writing of this page. They exist in Nightly, but as APIs get written they get added to Nightly and pushed through the trains. | |||
Focuses of the first release: | |||
* quality, stability and a base for many add-ons to move to | |||
* parity with Google Chrome and others on some (but not all APIs) | |||
* ability to build key add-ons that are not part of | |||
Application support: | |||
* Firefox | |||
* Firefox for Android (where APIs are appropriate) | |||
== APIs == | |||
Focus on key APIs that bring the biggest return for investment. Currently these are: alarms, browserAction, extension, i18n, notifications, runtime, storage, tabs, webNavigation and windows APIs. For the full list, look at the tracking bug {{Bugzilla|1214433}} | |||
== Development tools == | |||
Authors of WebExtensions add-ons should be able to develop easily their add-on locally, with support from tools like `jpm`. All APIs should be documented. | |||
== AMO == | |||
WebExtensions will be able to be uploaded to addons.mozilla.org then reviewed, searched, installed and updated just like any other Addon. | |||