WebExtensions/Applications - Revision history

DanielNL: added banner

2026-01-19T14:02:48Z

added banner

← Older revision		Revision as of 14:02, 19 January 2026
Line 1:		Line 1:
			{{Template:ObsoleteAMO}}

	Status: '''draft'''		Status: '''draft'''

Amckay: /* Loading in Firefox */

2017-10-18T16:58:06Z

Loading in Firefox

← Older revision		Revision as of 16:58, 18 October 2017
Line 61:		Line 61:

	When Firefox loads an add-on we would go through something like the following:		When Firefox loads an add-on we would go through something like the following:
	* see if browser_specific_settings > id exists in manifest.json
	** if an add-on id exists, use it for the add-on
	** continue on to the usual signing checks
	* see if applications > id exists in the manifest.json (for legacy)		* see if applications > id exists in the manifest.json (for legacy)
	** if an add-on id exists, use it for the add-on		** if an add-on id exists, use it for the add-on

Amckay: /* Submitting an add-on */

2017-10-18T16:52:27Z

Submitting an add-on

← Older revision		Revision as of 16:52, 18 October 2017
Line 44:		Line 44:

	When submitting a WebExtension we would go through something like the following:		When submitting a WebExtension we would go through something like the following:
	* see if browser_specific_settings > id exists in manifest.json
	** if an add-on id exists, use it for the add-on
	** continue
	* see if applications > id exists in the manifest.json (for legacy)		* see if applications > id exists in the manifest.json (for legacy)
	** if an add-on id exists, use it for the add-on		** if an add-on id exists, use it for the add-on

MikeKaply: Correct typo

2017-03-22T16:06:42Z

Correct typo

← Older revision		Revision as of 16:06, 22 March 2017
Line 19:		Line 19:
	"applications": {		"applications": {
	"gecko": {		"gecko": {
	"id": "drumpfinator-firefox@donaldjdrumpf.com",		"id": "drumpfinator-firefox@donaldjdrumpf.com"
	}		}
	}		}

Amckay: /* Loading in Firefox */

2016-04-05T21:41:38Z

Loading in Firefox

← Older revision		Revision as of 21:41, 5 April 2016
Line 66:		Line 66:
	* 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
	** continue		** continue on to the usual signing checks
	* see if applications > id exists in the manifest.json (for legacy)		* see if applications > id exists in the manifest.json (for legacy)
	** 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 on to the usual signing checks
	* if the add-on is signed		* if the add-on is signed
	** the add-on is contained in the signing in the CN field? (should check that) of the signature		** the add-on is contained in the signing in the CN field? (should check that) of the signature
	** use that add-on id		** use that add-on id
	** continue		** continue on to the usual signing checks
	* if the add-on id is not found and the add-on is being temporarily loaded through about:debugging		* if the add-on id is not found and the add-on is being temporarily loaded through about:debugging
	** generate a random add-on id		** generate a random add-on id

Amckay: /* Bugs, bugs */

2016-04-05T18:07:54Z

Bugs, bugs

← Older revision		Revision as of 18:07, 5 April 2016
Line 9:		Line 9:
	== Bugs, bugs ==		== Bugs, bugs ==

	Bugzilla: {{Bugzilla\|1255562}}, {{Bugzilla\|1255564}}		Bugzilla: {{Bugzilla\|1255562}} nope, this was replaced with {{Bugzilla\|1262005}}, {{Bugzilla\|1255564}}
	Github: https://github.com/mozilla/addons/issues/61		Github: https://github.com/mozilla/addons/issues/61

Amckay at 22:17, 4 April 2016

2016-04-04T22:17:30Z

← Older revision		Revision as of 22:17, 4 April 2016
Line 35:		Line 35:
	== Rename field ==		== Rename field ==

	Rename the field to '''browser_specific_settings'''~~, this is part of the first proposal for a standard for WebExtensions that will be discussed by the W3C group~~. If other ~~browser~~ support this key, then we can hope Chrome will start to ignore this key and not raise a warning in Chrome.		Rename the field to '''browser_specific_settings'''. If other browsers support this key, then we can hope Chrome will start to ignore this key and not raise a warning in Chrome.

	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.

Amckay: /* Signing */

2016-04-04T22:15:04Z

Signing

← Older revision		Revision as of 22:15, 4 April 2016
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.

	== ~~Signing~~ ==		== Submitting an add-on ==

	When ~~signing~~ a WebExtension we would go through something like the following:		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 ==

Amckay: /* Loading in Firefox */

2016-04-04T22:11:54Z

Loading in Firefox

← Older revision		Revision as of 22:11, 4 April 2016
Line 60:		Line 60:

	When Firefox loads an add-on we would go through something like the following:		When Firefox loads an add-on we would go through something like the following:
			* see if browser_specific_settings > id exists in manifest.json
			** if an add-on id exists, use it for the add-on
			** continue
	* see if applications > id exists in the manifest.json (for legacy)		* see if applications > id exists in the manifest.json (for legacy)
	** 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
	* see if browser_specific_settings > id exists in manifest.json
	** if an add-on id exists, use it for the add-on
	** continue
	* if the add-on is signed		* if the add-on is signed
	** the add-on is contained in the signing in the CN field? (should check that) of the signature		** the add-on is contained in the signing in the CN field? (should check that) of the signature

Amckay: /* Signing */

2016-04-04T22:11:27Z

Signing

← Older revision		Revision as of 22:11, 4 April 2016
Line 44:		Line 44:

	When signing a WebExtension we would go through something like the following:		When signing a WebExtension we would go through something like the following:
	* see if ~~applications~~ > id exists in ~~the~~ manifest.json ~~(for legacy)~~		* 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
	** continue		** continue
	* see if ~~browser_specific_settings~~ > id exists in manifest.json		* see if applications > id exists in the manifest.json (for legacy)
	** 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