Unfortunately, this seems to happen for NoScript too.
You can still download NoScript "Classic" (5.1.8.5) for Firefox 52 ESR here: it will be updated until June 2018, when ESR and the Tor Browser based on it will switch to 59.
https://noscript.net/getit
Well, this looks kind of gloomy, as NoScript and some sort of ad blocker would be two essential add-ons for me. I have read some of
The future of Seamonkey? -thread, and I guess have achieved some blurry understanding what is going on with Mozilla, Firefox and SeaMonkey.
What would be required for SeaMonkey development in practice, so that Firefox 57+ add-ons would work with it again? Just to add support for web extensions, to switch to same layout engine (Quantum) Firefox is using, aligning the source code with Firefox, or all these?
For aligning the source code, there seems to be a mention at SeaMonkey status meeting at 2017-09-03, which still remains open today:
frg suggests aligning the source with Fx after 2.56ESR. This means taking most parts of browser and put the old ui and mail integration on top. Reason is that porting bugs gets harder very day and web extensions plus e10s supports nedds to be added in the near future.
IanN thinks it might be a too huge task. The last time this was done more devs were available.
https://wiki.mozilla.org/SeaMonkey/Stat ... 2017-09-03