WebExtensions/Applications: Difference between revisions

 
(5 intermediate revisions by 2 users not shown)
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


Line 19: Line 19:
     "applications": {
     "applications": {
         "gecko": {
         "gecko": {
             "id": "drumpfinator-firefox@donaldjdrumpf.com",
             "id": "drumpfinator-firefox@donaldjdrumpf.com"
         }
         }
     }
     }
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.
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
Line 64: 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
* 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
Confirmed users
1,158

edits