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?
It’s not a standalone key, it’s a sub property of the applications
key.
1 Like
D’oh! Thanks.
From 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 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
jorgev
October 22, 2018, 10:18pm
4
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.
1 Like
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 then we’re at/around Full Web Page Screenshots (♥♥♥♥♥) :: Versions :: Add-ons for Firefox with:
Added multiprocess support for Firefox 48 and later versions
Firefox 48.0, See All New Features, Updates and Fixes (2016-08-02) scroll up (obtrusive banner)
★ new Process separation (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/ | LCARStrek – Add-ons for Firefox | caa:addon/lcarstrek not in the Classic Add-ons Archive, so I’m grabbing it quick before it disappears …