WebExtensions/RoadMapWebExt: Difference between revisions
No edit summary |
(adds core features section) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
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 the things we'd like to do in the future. | 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 the things we'd like to do in the future. | ||
These aren't in any particular order of priority. | These aren't in any particular order of priority and the road map may be outdated by the time you read this. | ||
=== Core features === | |||
* Allow web-ext options to be specified via config file | |||
=== Testing === | === Testing === | ||
Rather than focus on functionality like jpm test, we'd like to focus on: | This refers to giving extension developers some tools to help them write automated tests. Rather than focus on functionality like jpm test, we'd like to focus on: | ||
* Selenium | * Automating chrome-level browser interaction with Selenium | ||
* | * Writing unit tests using mock versions of the WebExtension API | ||
* Using static analysis to validate usage of the WebExtension API | |||
=== Other browsers === | === Other browsers === | ||
We'd like to be able to give support for other browsers, specifically: | We'd like to be able to give support for other browsers, specifically: | ||
* Firefox for Android | * Firefox for Android | ||
* Chrome | * Chrome | ||
* Opera | |||
* Edge | * Edge | ||
| Line 17: | Line 22: | ||
* allow web-ext run to open work in the browser | * allow web-ext run to open work in the browser | ||
* lint the extension to show which browser it works on | * lint the extension to show which browser it works on | ||
* auto-reload the extension in the browser as one edits the source (if possible) | |||
* remote debugging | * remote debugging | ||
Latest revision as of 16:36, 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 and the road map may be outdated by the time you read this.
Core features
- Allow web-ext options to be specified via config file
Testing
This refers to giving extension developers some tools to help them write automated tests. Rather than focus on functionality like jpm test, we'd like to focus on:
- Automating chrome-level browser interaction with Selenium
- Writing unit tests using mock versions of the WebExtension API
- Using static analysis to validate usage of the WebExtension API
Other browsers
We'd like to be able to give support for other browsers, specifically:
- Firefox for Android
- Chrome
- 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
- auto-reload the extension in the browser as one edits the source (if possible)
- 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.