Confirmed users
1,158
edits
WebExtensions/Applications: Difference between revisions
→Signing
| Line 41: | Line 41: | ||
The field is optional, developers can use it if they want to specify their add-on id in advance (for example if they are upgrading an old add-on to WebExtensions). Otherwise they can ignore it. | The field is optional, developers can use it if they want to specify their add-on id in advance (for example if they are upgrading an old add-on to WebExtensions). Otherwise they can ignore it. | ||
== | == Submitting an add-on == | ||
When | When submitting a WebExtension we would go through something like the following: | ||
* see if browser_specific_settings > id exists in manifest.json | * see if browser_specific_settings > id exists in manifest.json | ||
** if an add-on id exists, use it for the add-on | ** if an add-on id exists, use it for the add-on | ||
| Line 50: | Line 50: | ||
** if an add-on id exists, use it for the add-on | ** if an add-on id exists, use it for the add-on | ||
** continue | ** continue | ||
* generate a new add-on id, add it to the AMO table for that add-on | * generate a new add-on id, add it to the appropriate AMO table for that add-on | ||
The add-on developer can find their add-on id by: | The add-on developer can find their add-on id by: | ||
| Line 56: | Line 56: | ||
* using the API? | * using the API? | ||
* ... should we do more here? | * ... should we do more here? | ||
=== Signing an add-on === | |||
Each time the add-on is signed (for each version), it will pull the add-on id out of the appropriate AMO table and sign it with that add-on id. The add-on id will be in the signature and be consistent for each version of that add-on. | |||
== Loading in Firefox == | == Loading in Firefox == | ||