Confirmed users
1,158
edits
WebExtensions/RoadMapFirefox57: Difference between revisions
→Toolbars
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
Related documents: [https://wiki.mozilla.org/WebExtensions/Vision a vision for WebExtensions]. | Related documents: [https://wiki.mozilla.org/WebExtensions/Vision a vision for WebExtensions]. | ||
This document tries to explain the development roadmap between now and the Firefox 57 release. It does not try to predict changes or new APIs beyond that, rather to give a clear roadmap to developers who might be porting their add-on to WebExtensions. If you are | This document tries to explain the development roadmap between now and the Firefox 57 release. It does not try to predict changes or new APIs beyond that, rather to give a clear roadmap to developers who might be porting their add-on to WebExtensions. If you are porting your add-on, [https://wiki.mozilla.org/Add-ons/developer/communication some help is available]. | ||
Because WebExtensions are an open source project, the exact amount of work that’s completed between now and [https://wiki.mozilla.org/RapidRelease/Calendar Firefox 57] will depend upon the amount of contributions. Our aim is to complete all bugs marked as [https://mzl.la/2pkdX0R webextensions+] in Bugzilla before Firefox 57. We are expecting regressions, security issues to be added to this list. | Because WebExtensions are an open source project, the exact amount of work that’s completed between now and [https://wiki.mozilla.org/RapidRelease/Calendar Firefox 57] will depend upon the amount of contributions. Our aim is to complete all bugs marked as [https://mzl.la/2pkdX0R webextensions+] in Bugzilla before Firefox 57. We'll then review all bugs marked as webextensions?. We are expecting regressions, security issues and performance issues to be added to this list of work we have to do as high priorities. | ||
=== Chrome compat. === | === Chrome compat. === | ||
The work on Chrome compatibility is mostly complete. There are edge cases or low priority bugs to be completed, but by 57 we support some level of the following APIs: alarms, bookmarks, browserAction, browsingData, commands, contextMenus, cookies, devtools.inspectedWindow, devtools.network, devtools.panels, downloads, extension, history, i18n, identity, idle, management, notifications, omnibox, pageAction, permissions, privacy.network, privacy.websites, proxy, runtime, sessions, storage, tabs, topSites, webNavigation, webRequest, windows. | The work on Chrome compatibility is mostly complete. There are edge cases or low priority bugs to be completed, but by 57 we support will some level of the following APIs: alarms, bookmarks, browserAction, browsingData, commands, contextMenus, cookies, devtools.inspectedWindow, devtools.network, devtools.panels, downloads, extension, history, i18n, identity, idle, management, notifications, omnibox, pageAction, permissions, privacy.network, privacy.websites, proxy, runtime, sessions, storage, tabs, topSites, webNavigation, webRequest, windows. | ||
We also have support for nativeMessaging and things that are not in Chrome such as: sidebars, contextualIdentities and theme. | |||
For a full list of APIs see [https://developer.mozilla.org/en-US/Add-ons/WebExtensions MDN] (the definitive source) or [https://arewewebextensionsyet.com/ arewewebextensionsyet.com]. For an outline of our compat policy, please read the [https://blog.mozilla.org/addons/2016/09/13/webextensions-and-parity-with-chrome/ blog post]. | For a full list of APIs see [https://developer.mozilla.org/en-US/Add-ons/WebExtensions MDN] (the definitive source) or [https://arewewebextensionsyet.com/ arewewebextensionsyet.com]. For an outline of our compat policy, please read the [https://blog.mozilla.org/addons/2016/09/13/webextensions-and-parity-with-chrome/ blog post]. | ||
| Line 17: | Line 17: | ||
=== Out of process extensions === | === Out of process extensions === | ||
Before Firefox 57 lands, we will complete out of process extensions. | Before Firefox 57 lands, we will complete out of process extensions. Content scripts already run in the content process. This change will mean the rest of the extension will now run in an extension process. There will be one process for all the extensions. This will include a suitable set of metrics to measure the performance of the extension process and content script. | ||
=== Developer tools === | === Developer tools === | ||
We aim to complete the developer tools APIs (inspectedWindow and panels) to the degree that the most popular devtools add-ons ([https://chrome.google.com/webstore/detail/ember-inspector/bmdblncegkenkacieihfhpjfppoconhi Ember Inspector], [https://chrome.google.com/webstore/detail/angularjs-batarang/ighdmehidhipcmcojjgiloacoafjmpfk Angular JS Batarang], [https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi React Dev Tools], [ | We aim to complete the developer tools APIs (inspectedWindow and panels) to the degree that the most popular devtools add-ons ([https://chrome.google.com/webstore/detail/ember-inspector/bmdblncegkenkacieihfhpjfppoconhi Ember Inspector], [https://chrome.google.com/webstore/detail/angularjs-batarang/ighdmehidhipcmcojjgiloacoafjmpfk Angular JS Batarang], [https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi React Dev Tools], [https://chrome.google.com/webstore/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd Redux DevTools Extension]) on the Chrome store will work in Firefox with minimal or no modification. | ||
https://chrome.google.com/webstore/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd Redux DevTools Extension]) on the Chrome store will work in Firefox with minimal or no modification. | |||
=== Android === | === Android === | ||
| Line 52: | Line 51: | ||
=== Toolbars === | === Toolbars === | ||
This [https://bugzilla.mozilla.org/show_bug.cgi?id=1215064 bug] suggests it will be happening, but it hasn't been assigned to anyone yet. There's some discussion around if this is a good feature or not. The only toolbar left in Firefox is the bookmarks toolbar and there's some pressure to remove that as well. We are not keen on providing APIs, only to have to remove them. | |||
Of all the things in the roadmap, this is the most unclear at this moment. [Last updated May 9th] | |||
This is not going to happen for Firefox 57. | |||
[Last updated August 16th] | |||
=== Theming === | === Theming === | ||