WebExtensions/Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This is an initial roadmap of WebExtensions.
This document provides the overview of timelines androad maps for WebExtensions.


Status: '''draft, in progress'''.
Please refer to the vision document for [http://wiki.mozilla.org/WebExtensions/Vision overview of where WebExtensions are heading].


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.
= Timelines =


= WebExtensions 1.0 =
Please also see [https://wiki.mozilla.org/Electrolysis#Add-ons_Schedule Multiprocess Firefox up to 57] timeline.


Focuses of the first release:
{| class="wikitable"
* quality, stability and a base for many add-ons to move to
|-
* parity with Google Chrome and others on some (but not all APIs)
! Release !! Platform !! Description
* ability to build key add-ons that are not part of  
|-
| 55 || Firefox Desktop || Disabling non-MPC add-ons on Nightly *only*.
|-
| 56 ||  || No changes planned.
|-
| 57 || Firefox || WebExtensions and internal Mozilla add-ons only. For details of what will be allowed see [https://wiki.mozilla.org/Add-ons/Firefox57 this page].
|
|}


Application support:
= APIs =
* Firefox
* Firefox for Android (where APIs are appropriate)


== APIs ==
The following links outline out APIs expect to be landing in what release:


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}}
* [https://wiki.mozilla.org/WebExtensions/RoadMapFirefox48 Up to Firefox 48]
 
* [https://wiki.mozilla.org/WebExtensions/RoadMapFirefox57 Up to Firefox 57]
== 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 {{Bugzilla|1210037}}
 
== Timeline ==
 
By the end of Q2 2016.
 
== Deprecations ==
 
We don't anticipate that this release will cause any deprecations of other ways of building add-ons, although certainly we'd hope most resource will go into this release.
 
= WebExtensions Themes - scratch pad =
This is our area to free form work through upcoming ideas, a scratch pad for priority & planning
*native.js [https://bugzilla.mozilla.org/show_bug.cgi?id=1199718 Bug 1199718] - making it easy/faster for folks to prototype webextensions to build API’s
**with this we can dev in 2 weeks and have big benefit from this for a long time.
***goal: tested, prototyped, pushed into mozcentral when ready “ideatown for webextension api’s” (Philip, Andy, John G - since similar to ideatown)
**timing: UX work after e10s interface [https://bugzilla.mozilla.org/show_bug.cgi?id=1181835 bug 1181835]
**what is in development? about:config list add-ons using native js
*chrome parity
*chrome add-ons porting
**top 20 chrome add-ons run in Fx
*firefox add-ons porting
**top 20 firefox add-ons running in WebExtensions - criteria based on downloads, actual usage, ratings: typically adblockers, download managers, tab add-ons, etc.
*eg: the SDK proposal from Luca
*unique to Firefox features - get ideas in this cycle for next….
**driven by add-ons need
**ex: Bug 1244789 - Support richer user interactions in the chrome.browserAction API (Giorgio dev side / aswan andy would like to help engage here, madhava, markus)
**ex: [https://bugzilla.mozilla.org/show_bug.cgi?id=1219940 Bug 1219940 ] Something equivalent to OS.File - native.js would help until it's done as a "regular" WebExtension API
*[https://wiki.mozilla.org/WebExtensions/GoFaster go faster] - early feasibility planning starting
**feasibility (can we do it, difficulty, when good time)
**open issues as it's ramping up (laura's team)
*runtime.connectnative
*Styling & sort order - UX is lower priority for now

Latest revision as of 16:22, 9 May 2017

This document provides the overview of timelines androad maps for WebExtensions.

Please refer to the vision document for overview of where WebExtensions are heading.

Timelines

Please also see Multiprocess Firefox up to 57 timeline.

Release Platform Description
55 Firefox Desktop Disabling non-MPC add-ons on Nightly *only*.
56 No changes planned.
57 Firefox WebExtensions and internal Mozilla add-ons only. For details of what will be allowed see this page.

APIs

The following links outline out APIs expect to be landing in what release: