WebExtensions/RoadMapWebExt: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The [https://github.com/mozilla/web-ext web-ext command line] tool is for developing WebExtensions. This document tries to outline a roadmap for web-ext. This roadmap outlines...") |
No edit summary |
||
| Line 20: | Line 20: | ||
=== Boilerplate === | === Boilerplate === | ||
Through the web-ext create command we can allow new templates to be created. These templates would be for things like: | Through the web-ext create command we can allow new templates to be created. These templates would be for things like: babel, webpack, the polyfill and test mocking. | ||
=== AMO APIs === | === AMO APIs === | ||
The ability to upload a listed version to AMO has been a common request, as opposed to just signing. There might be more we can do here. | The ability to upload a listed version to AMO has been a common request, as opposed to just signing. There might be more we can do here. | ||
Revision as of 16:20, 5 July 2017
The web-ext command line tool is for developing WebExtensions. This document tries to outline a roadmap for web-ext. This roadmap outlines the things we'd like to do in the future.
These aren't in any particular order of priority.
Testing
Rather than focus on functionality like jpm test, we'd like to focus on:
- Selenium
- Testing using mocks
Other browsers
We'd like to be able to give support for other browsers, specifically:
- Firefox for Android
- Chrome and Opera
- Edge
The support would be for:
- allow web-ext run to open work in the browser
- lint the extension to show which browser it works on
- remote debugging
Boilerplate
Through the web-ext create command we can allow new templates to be created. These templates would be for things like: babel, webpack, the polyfill and test mocking.
AMO APIs
The ability to upload a listed version to AMO has been a common request, as opposed to just signing. There might be more we can do here.