Stylish and Stylem appear broken in new release.

[tyukok]

I've been using Stylem for all my user-styling needs, but after updating to 2.53.13 it doesn't work now - it's missing some of its UI (for example, "Create new style" menu just shows blank submenu on mouse hover), no options seem to work, and none of my userstyles work too. Stylish has the same problem too.
What could be causing the problem?

[n0spam]

Most likely, because someone forgot to take their pills (again):

Removal of array comprehensions, legacy iterators and generators bug 1414340 and bug 1098412.

JavaScript console (Ctrl+Shift+J) should have some clues in form of error messages.

[tyukok]

JavaScript console (Ctrl+Shift+J) should have some clues in form of error messages.

Here's the output when I click on Stylem icon in the navbar:

TypeError: stylishOverlay is undefined navigator.xul:1:1
onpopupshowing chrome://navigator/content/navigator.xul:1:1

[tyukok]

Ok, so I looked it up, and apparently Stylish used to exhibit the same issue with Firefox 57: https://github.com/stylish-userstyles/s ... issues/318
A comment in the discussion linked above pointed to various fixes that were done to make it work again (it took them awhile to switch to WebExtensions, so some people maintained the legacy version for some time prior to that, when Firefox Quantum still supported the old XUL add-ons): https://github.com/stylish-userstyles/s ... 19/commits
Once I applied these fixes to Stylem (which itself is a Pale Moon-specific fork of a legacy version of Stylish), everything worked!

I think I'll make an account on addons.thunderbird.net and post the edited version there.

[therube]

(If not TB, at least simply throw up a link somewhere to your modified file...)

[frg]

https://github.com/Lootyhoof/stylem/releases/tag/v2.2.8

Not sure if the above addresses all issues with 2.53.13. If not this one does:
https://github.com/dirkf/stylem/releases/tag/2.2.8-df

[therube]

Yeah I put in Lootyhoof's 2.2.8 earlier & saw that it did "run".
(That said, I know nothing of it, so no idea if it ran "correctly".)

Given that dirkf mentions the same issue that tyukok pointed out...

[tyukok]

Can confirm, version 2.2.8 works exactly as it should.
Glad they now target SeaMonkey directly.