[CLOSED] Noscript is crashing Add-ons Manager

[Death2Gnomes]

I've had to start from scratch (my ssd took a dump), so after installing Noscript, using the Add-ons Manager, the "Get Add-ons" tab/page is freezing up and crashing Waterfox. Now What?

[therube]

Do you get crash reports, about:crashes, in Waterfox?
If so, what are the last few related crash report URLs?

[barbaz]

Waterfox is not a supported browser. Do you see this problem in Firefox or SeaMonkey?

[Death2Gnomes]

I've used WF for years and never had a problem wit Noscript.

I get about:crashes as an invalid address.

So assuming it was a corrupt install, is it safe to delete references to noscript in about:config to do a clean install?

[barbaz]

Yep, that should get you a clean install of NoScript. You could also just do NoScript Options > Reset, then confirm that you want "ALL the NoScript preferences and site permissions will be reset to their default values immediately."

[Death2Gnomes]

Ok figured it out, what a PITA, musta have restarted WF 20 times. Change one setting at a time, and back again. Whatever is being blocked on that page, its something in ABE thats doing it, currently ABE is not enabled until i get all my previous add-ons re-installed. So whats next?

[barbaz]

Again, do you see this problem in a supported browser?

[Death2Gnomes]

Again, do you see this problem in a supported browser?

As I said, I've used Waterfox (formerly known as Firefox 64) since it split off from Firefox, and never had such an issue with Noscript in all these years. This is new issue with the recent build. I really dont know how to change ABE settings effectively to do any real testing. So asking if this a problem in a supported browser is kinda stupid.

[Death2Gnomes]

No offense meant.

[barbaz]

If you're not willing to test a supported browser then we won't be able to help you. We're all volunteers doing support here in our spare time, and none of us have any experience with Waterfox. We don't know how to troubleshoot problems on Waterfox. And I know from experience it's not safe to assume that these third-party builds work exactly the same as Firefox.

If this problem occurs in a supported browser, let us know and we'll see what we can come up with.

[Death2Gnomes]

If you're not willing to test a supported browser then we won't be able to help you. We're all volunteers doing support here in our spare time, and none of us have any experience with Waterfox. We don't know how to troubleshoot problems on Waterfox. And I know from experience it's not safe to assume that these third-party builds work exactly the same as Firefox.

If this problem occurs in a supported browser, let us know and we'll see what we can come up with.

I really dont see what the problem is here. Waterfox is originally Firefox. So much of the same code that 99% of all add-ons written for the 32 bit firefox actually works as intend in Waterfox. Now I gave you the problem area for this one specific issue and which specific area of noscript that is causing it. I dont use "your supported browsers" for a reason, the flipside is that many dont use Warefox "cuz its too hard to code in it", so it goes on way many unsupported browser lists. A sure sign of lazyness or some similar attitude.

As of this moment I have all features of Noscript enabled and as long as I dont go to the Get Addons page in the Addons Manager, I have no issue. Take it for what it is. I wont be coming back, you are trying to force me to do something I dont want to do, its not my Addon, there are others that work perfectly fine too.

[barbaz]

I wont be coming back,

OK. Bye.

Locking as there is no need to reply here anymore.