InformAction Forums

Hi folks
I still use occasionnally a 2014 Mac Mini running MacOS 10.9.5. I browse with the last compatible Firefox version 78.15.
In NoScript the Allow automatic updates option was checked by default. It worked seamlessly until lately when NS was updated to version 11.4.34 and ceased to work entirely. The menu icon is inactive.
Is it possible to come back to an earlier version?
TIA
Regards
Nick

Yes. Old NoScript @
https://addons.mozilla.org/addon/noscript/versions
*or*
https://noscript.net/feed?quantum&c=100

Can confirm the issue. OP understated the breakage: the NoScript toolbar icon doesn't open the popup, NoScript Options is just an uninitialized mess, and webpages seem to hang loading.

The relevant error in Browser Console is probably this - referencing this line - https://github.com/hackademix/nscl/blob ... ge.js#L130

But ||= requires Firefox >= 79. But NoScript's stated minimum version requirement wasn't increased.

I guess it was an oversight that the Noscript creator missed

maybe use the much older 10.1.7.3 version for FireFox 78.x

4td8s wrote: ↑Fri Aug 09, 2024 5:06 pm maybe use the much older 10.1.7.3 version for FireFox 78.x

Why? What's broken with NoScript 11.4.31 on Firefox 78.15esr?

Hi
Thank you folks for your quick responses.
IMHO NS 11.4.34 is not at fault. I am running it on my M1 MacBook and it works just fine. The issue is the incompatibility with my very old version of FF. I keep this old Mini because I occasionally need to use legacy softs because either they are discontinued or I don't want to upgrade them.
The issue occurred very recently so I suppose the versions prior to 11.4.34 are OK.
So I suppose I just need to remove NS from FF and then download the version that's safe, right?
Thanks for the tips and the links.
Nick

Guest wrote: ↑Fri Aug 09, 2024 10:10 pm IMHO NS 11.4.34 is not at fault.

As long as NoScript declares compatibility with FF 78, any incompatibility with FF 78 is a NoScript bug.

Guest wrote: ↑Fri Aug 09, 2024 10:10 pm So I suppose I just need to remove NS from FF and then download the version that's safe, right?

No. Don't remove NoScript as this may delete some of your NoScript configuration.

I would

• first disable automatic updating of NoScript,
• then disable NoScript (keeping it installed),
• then install the version that's "safe" (11.4.31) on top,
• then re-enable NoScript.

barbaz wrote: ↑Sat Aug 10, 2024 12:15 am As long as NoScript declares compatibility with FF 78, any incompatibility with FF 78 is a NoScript bug.

Well, let's say it's a bug in the installer.

barbaz wrote: ↑Sat Aug 10, 2024 12:15 am first disable automatic updating of NoScript,
then disable NoScript (keeping it installed),
then install the version that's "safe" (11.4.31) on top,
then re-enable NoScript.

Bingo!
It worked as a charm and moreover it was almost instantaneous!
Thanks a lot!
Nick

I couldn't find how to mark this topic as resolved.

Guest wrote: ↑Sat Aug 10, 2024 1:44 pm I couldn't find how to mark this topic as resolved.

It isn't resolved until either fixing the incompatibility with FF 78 or increasing NoScript's minimum Firefox version requirement to what's actually compatible/supported.

If Giorgio doesn't see this thread, this might be worth an issue at NSCL issue tracker, especially since NoScript is the flagship user of NSCL.

barbaz wrote: ↑Sat Aug 10, 2024 3:48 pm It isn't resolved until either fixing the incompatibility with FF 78 or increasing NoScript's minimum Firefox version requirement to what's actually compatible/supported.

The issue is at least resolved for me.

barbaz wrote: ↑Sat Aug 10, 2024 3:48 pm If Giorgio doesn't see this thread, this might be worth an issue at NSCL issue tracker, especially since NoScript is the flagship user of NSCL.

I registered to the site but I never got an activation e-mail. I wrote a mail about the issue but I am still not an active member.

Fixed in latest development build 11.4.35rc1?