Note that this key is not supported by Blink-based browsers (Google Chrome and Opera). If you include this key in an add-on, and load it into one of these browsers, it will show a warning, but will still work.

Type Object
Mandatory Usually, no (but see also When do you need an Add-on ID?). Mandatory before Firefox 48.
Example
"applications": {
  "gecko": {
    "id": "addon@example.com",
    "strict_min_version": "42.0"
  }
}

The applications key contains keys that are specific to a particular host application.

Currently this contains just one key, gecko, which may contain four string attributes:

  • id is the extension ID. Optional from Firefox 48, mandatory before Firefox 48. See WebExtensions and the Add-on ID to see when you need to specify an add-on ID.
  • strict_min_version: minimum version of Gecko to support. Versions containing a "*" are not valid in this field. Defaults to "42a1". Requires Gecko 45
  • strict_max_version: maximum version of Gecko to support. If the Firefox version on which the extension is being installed or run is above this version, then the extension will be disabled, or not permitted to be installed. Defaults to "*", which disables checking for a maximum version. Requires Gecko 45
  • update_url is a link to an add-on update manifest. Note that the link must begin with "https". This key is for managing extension updates yourself (i.e. not through AMO). Requires Gecko 45

Chrome incompatibilities

You can't use this key in Chrome extensions.

Examples

Example with all possible keys. Note that you will normally include neither a strict_max_version nor a update_url key in most add-ons.

"applications": {
  "gecko": {
    "id": "addon@example.com",
    "strict_min_version": "42.0",
    "strict_max_version": "50.*",
    "update_url": "https://example.com/updates.json"
  }
}

Document Tags and Contributors

 Contributors to this page: Makyen, wbamberg, andymckay, bsilverberg, m_gol, lv7777, kmaglione, dirty-bit, AlexPl
 Last updated by: Makyen,