Confirmed users
1,158
edits
WebExtensions/Experiments: Difference between revisions
Jump to navigation
Jump to search
→Overview
No edit summary |
|||
| Line 7: | Line 7: | ||
As we move to a world of WebExtensions for add-ons we need to be able to provide more APIs than ever before to our users. We need to be able to go beyond what chrome provides to allow more flexibility and customisation than other browsers. | As we move to a world of WebExtensions for add-ons we need to be able to provide more APIs than ever before to our users. We need to be able to go beyond what chrome provides to allow more flexibility and customisation than other browsers. | ||
At the same time, we need to be able to move faster than the Firefox train and allow developers to be able to quickly develop and experiment with APIs. Those APIs would land in an add-on and as APIs become stable and supported they could be moved down into mozilla-central and move from "experimental" to "stable". | |||
To repeat, this is the overall goal: '''be an area to allow developers to develop and experiment with APIs'''. | To repeat, this is the overall goal: '''be an area to allow developers to develop and experiment with APIs'''. | ||
Key points: | Key points: | ||
* We would land experimental APIs in an add-on outside of Firefox. | |||
* There would be only one WebExtensions Experiments add-on. | * There would be only one WebExtensions Experiments add-on. | ||