We'd like to be able to get web extensions on to AMO. There are some areas we know we have to fix and some areas we need to test and see how they work. These include but are not limited to: * checking the add-on in the validator * signing the add-on * reviewing the add-on * viewing and installing the add-on * update checks as the add-on updates We know the validator has to be changed, not sure on the rest.
And also submitting the add-on to AMO: I guess we'll need a new "Extractor" subclass (https://github.com/mozilla/olympia/blob/a926e1d7f2323c778e638bf82483ae45372608f3/apps/files/utils.py#L86) to deal with the new manifest.json format.
For viewing and installing the add-ons it would be great to get to a simpler way of installing add-ons, maybe like suggested in bug 1153226. And surfacing the powers of specific add-ons, maybe as permissions might be useful to better understand what add-ons can do. And while I am at it, showing the impact on performance an add-on will have would be great as well.
Any word on an official release date for the web extension api.
(In reply to aneury.casado from comment #4) > Any word on an official release date for the web extension api. Their wiki says a timeline of Q2 2016 (source: https://wiki.mozilla.org/WebExtensions/RoadMap)
This is turned on and everything else is being tracked in github: https://github.com/mozilla/olympia/issues?q=is%3Aopen+is%3Aissue+label%3AWebExtensions
Any idea why when I submit a WebExtension to AMO, it doesn't use i18n and detects my extension name as "__MSG_name__"?
^ any idea?
This bug hadn't landed yet: https://github.com/mozilla/addons-server/issues/1681 It landed on Thursday (7th) and should work. Please file issues in github if it doesn't.