Confirmed users
1,158
edits
WebExtensions/Applications: Difference between revisions
no edit summary
(→Proposal: - Add compatibility checks) |
No edit summary |
||
| Line 31: | Line 31: | ||
Add-on developers could keep track of their add-on along with add-on if they so with, but it won't interfere with the basic operation of the add-on. | Add-on developers could keep track of their add-on along with add-on if they so with, but it won't interfere with the basic operation of the add-on. | ||
== Signing == | == Signing == | ||
| Line 80: | Line 76: | ||
We'd have to alter the validator with the changes to the files and make the applications and mozilla.json optional. | We'd have to alter the validator with the changes to the files and make the applications and mozilla.json optional. | ||
= Out of scope = | |||
== Compatibility == | |||
Compatibility checks for Chrome Add-ons submitted to AMO and/or for signing would be required. Add-ons that use unsupported APIs should be flagged and/or rejected to avoid user confusion/consternation. | |||
Please see [https://github.com/mozilla/addons-server/issues/1337 bug 1337]. | |||