# Documentation for strict\_min\_version in manifest.json

**URL:** https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672
**Category:** MDN
**Tags:** learning
**Created:** [October 19, 2018, 12:59am UTC](https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672 "2018-10-19T00:59:58Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![grahamperrin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/grahamperrin/32/17266_2.png) [@grahamperrin](https://discourse.mozilla.org/u/grahamperrin)
#### Post date: [October 19, 2018, 12:59am UTC](https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672/1 "2018-10-19T00:59:58Z")

</div>

[https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/manifest.json#Example](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/manifest.json#Example) exemplifies use of `strict_min_version` but nearer the head of the page, there’s no bullet pointed link for it; `https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/strict_min_version` does not exist.

Please, where is the documentation?

---

<div class="post-metadata">

### Author: ![wbamberg](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/wbamberg/32/30597_2.png) [@wbamberg](https://discourse.mozilla.org/u/wbamberg)
#### Post date: [October 19, 2018, 2:21am UTC](https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672/2 "2018-10-19T02:21:14Z")

</div>

It’s not a standalone key, it’s a sub property of the [`applications`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/applications) key.

---

<div class="post-metadata">

### Author: ![grahamperrin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/grahamperrin/32/17266_2.png) [@grahamperrin](https://discourse.mozilla.org/u/grahamperrin)
#### Post date: [October 19, 2018, 2:53am UTC](https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672/3 "2018-10-19T02:53:44Z")

</div>

D’oh! Thanks.

From [https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/manifest.json/applications#Firefox\_(Gecko)\_properties](https://developer.mozilla.org/docs/Mozilla/Add-ons/WebExtensions/manifest.json/applications#Firefox_(Gecko)_properties):

> Defaults to “42a1”.

Is that still true?

[Requirements · Issue #2 · bgpat/anchor-selector · GitHub](https://github.com/bgpat/anchor-selector/issues/2#issuecomment-431114634) observed:

> > > Works with Firefox for Android 48.0 and later, Firefox 48.0 and later

… is there, I wonder, a different default at AMO when things are not specified at AMO? @jorgev

---

<div class="post-metadata">

### Author: ![jorgev](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jorgev](https://discourse.mozilla.org/u/jorgev)
#### Post date: [October 22, 2018, 10:18pm UTC](https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672/4 "2018-10-22T22:18:43Z")

</div>

Yes, it looks like new submissions without a `strict_min_version` default to 48.0 as the min version. I don’t know when that was introduced or why. Would need to dig into the AMO code to try to find that out.

---

<div class="post-metadata">

### Author: ![grahamperrin](https://sea1.discourse-cdn.com/flex001/user_avatar/discourse.mozilla.org/grahamperrin/32/17266_2.png) [@grahamperrin](https://discourse.mozilla.org/u/grahamperrin)
#### Post date: [October 22, 2018, 11:41pm UTC](https://discourse.mozilla.org/t/documentation-for-strict-min-version-in-manifest-json/32672/5 "2018-10-22T23:41:21Z")

</div>

OK, I put myself into _Step Away from The Computer_ mode and thought:

> “What do I most associate with **Firefox 48**?”

Answer: **SeaMonkey** (don’t ask me why) and if we ignore the first result at [Google Search](https://www.google.com/search?q=%22Firefox+48%22+%2B%22SeaMonkey%22) then we’re at/around [Full Web Page Screenshots (♥♥♥♥♥) :: Versions :: Add-ons for Firefox](http://web.archive.org/web/20181002002702/https://addons.mozilla.org/en-US/firefox/addon/fireshot/versions/?page=1#version-0.98.88) with:

> - Added multiprocess support for Firefox 48 and later versions

[Firefox 48.0, See All New Features, Updates and Fixes](https://www.mozilla.org/firefox/48.0/releasenotes/#note-786661) (2016-08-02) ▶ scroll up (obtrusive banner)

> **★ new** [Process separation](https://blog.mozilla.org/futurereleases/2016/08/02/whats-next-for-multi-process-firefox/) (e10s) is enabled for some of you. …

* * *

So @jorgev my lazy guess:

- 48 was the point at./around which AMO began determining whether submissions were compatible with e10s.

* * *

Now for me it’s back to that top result in Google, [https://addons.mozilla.org/addon/lcarstrek/](https://addons.mozilla.org/addon/lcarstrek/) | [LCARStrek – Add-ons for Firefox](http://web.archive.org/web/20180730113022/https://addons.mozilla.org/en-US/firefox/addon/lcarstrek/) | caa:addon/lcarstrek _not_ in the Classic Add-ons Archive, so I’m grabbing it quick before it disappears … 🙂
