Firefox 108+ getting stricter about extension version format?

Bug reports and enhancement requests
Post Reply
barbaz
Senior Member
Posts: 10841
Joined: Sat Aug 03, 2013 5:45 pm

Firefox 108+ getting stricter about extension version format?

Post by barbaz »

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 -

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 dots
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?
*Always* check the changelogs BEFORE updating that important software!
-
User avatar
Giorgio Maone
Site Admin
Posts: 9454
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Firefox 108+ getting stricter about extension version format?

Post by Giorgio Maone »

The bug appears closed.
However I've commented static our case and linking this thread.
Mozilla/5.0 (X11; Linux x86_64; rv:107.0) Gecko/20100101 Firefox/107.0
barbaz
Senior Member
Posts: 10841
Joined: Sat Aug 03, 2013 5:45 pm

Re: Firefox 108+ getting stricter about extension version format?

Post by barbaz »

Thanks Giorgio.
Giorgio Maone wrote: Tue Dec 13, 2022 10:05 pm The bug appears closed.
However
My understanding was that the closing was not the end of that bug, but that the bug was moved to a Github issue, where it was decided that the Toolkit-style version format is already officially deprecated and will be definitely disallowed in Firefox Manifest V3, and maybe even Manifest V2 at some point. And that although there are no immediate plans to make the Firefox browser enforce the version format, it *will* be enforced at least for signed addons (which NoScript dev builds are signed). Am I misunderstanding?
*Always* check the changelogs BEFORE updating that important software!
-
Post Reply