Firefox 108+ getting stricter about extension version format?
Posted: Tue Dec 13, 2022 4:15 pm
Just saw this -
https://bugzilla.mozilla.org/show_bug.cgi?id=1793925
https://bugzilla.mozilla.org/show_bug.cgi?id=1593316#c5
And it affects NoScript dev builds -
I thought maybe NoScript dev builds could use version_name, as I've done for local Chromium extensions where this was a problem. But that's not supported in Firefox - https://bugzilla.mozilla.org/show_bug.cgi?id=1380219
How will NoScript dev builds handle this?
https://bugzilla.mozilla.org/show_bug.cgi?id=1793925
https://bugzilla.mozilla.org/show_bug.cgi?id=1593316#c5
And it affects NoScript dev builds -
Code: Select all
addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}': Reading manifest: Warning processing version: version must be a version string consisting of at most 4 integers of at most 9 digits without leading zeros, and separated with dots
addons.webextension.{73a6fe31-595d-460b-a920-fcc0f8843232} WARN Loading extension '{73a6fe31-595d-460b-a920-fcc0f8843232}': Reading manifest: Warning processing version: version must be a version string consisting of at most 4 integers of at most 9 digits without leading zeros, and separated with dotsHow will NoScript dev builds handle this?