NoScript not working in Firefox - leaving me vulnerable

[friedchicken]

I'm running Mac OS X Mojave

Latest version of Firefox

running the following extensions: noscript, torrentconrol, ublock origin, downie, sponsorblock, return youtube dislike, facebook container.

I have no indication that noscript is working: no broken websites requiring js, no nothing.
I've tried individually disabling extensions, but no avail.

I'm sorry to just register and post here, what's not being posted is literally YEARS of flawless use and appreciation for this extension. There is no similar script blocker for safari, and it makes safari a dealbreaker for me.

Thank you for the help!

[Giorgio Maone]

Hi, could you please send me your NoScript Options>Export file for examination?
My email address (and PGP key) is on the top right of https://maone.net.

[friedchicken]

Just sent!

[Giorgio Maone]

Just sent!

Seen, and mistery probably solved: it seems you accidentally selected the "Disable restrictions globally (dangerous)" option. Just uncheck it in NoScript Options>General.

[friedchicken]

Just sent!

Seen, and mistery probably solved: it seems you accidentally selected the "Disable restrictions globally (dangeros)" option. Just uncheck it in NoScript Options>General.

Weird that I didn't notice this. I've never touched those settings.

[Giorgio Maone]

Just sent!

Seen, and mistery probably solved: it seems you accidentally selected the "Disable restrictions globally (dangeros)" option. Just uncheck it in NoScript Options>General.

Weird that I didn't notice this. I've never touched those settings.

You might accidentally enable it from the popup as well, it's the "S" button with the exlamation mark (S!). You can hide it by drag & drop if you're afraid to hit it again.

[musonius]

There are so many cases where people accidentally set the "Disable restrictions globally (dangerous)" option. What's the reason for not making it temporary?

[Giorgio Maone]

There are so many cases where people accidentally set the "Disable restrictions globally (dangerous)" option. What's the reason for not making it temporary?

I'm rather thinking of making it more obvious (e.g. by disabling all the per-site permissions UI in the popup as well, when it's checked), and maybe adding a confirmation prompt with the option to make it either session-temporary or permanent.

[friedchicken]

Something to indicate this is the case would be *very* helpful.

It could also be useful that I can still set the permissions, so I can use noscript with all my webpages working, but still go through and click what I want to allow/disallow, then when I re-enable it, not deal with the hassle.

[musonius]

I'm rather thinking of making it more obvious (e.g. by disabling all the per-site permissions UI in the popup as well, when it's checked), and maybe adding a confirmation prompt with the option to make it either session-temporary or permanent.

I think that would be perfect!

[aarno]

I too have been caught out by the "Disable Restrictions Globally" feature and I could have sworn that NoScript used to warn you vigorously NOT TO DO THIS, DO SO AT YOUR OWN RISK.

But I never received such a warning when I (possibly) accidentally clicked this option.

Anyway, I would be all for a giant pop up box or some sort of warning tell me to not do this, as the cases for doing so are very few and far between for the majority of average users, I feel.

Thanks for the great product

It is much appreciated.

If I have a good lottery win, you will be one of the first to no about it.

[Giorgio Maone]

Anyway, I would be all for a giant pop up box or some sort of warning tell me to not do this, as the cases for doing so are very few and far between for the majority of average users, I feel.

Done in latest development build, thanks:
v 11.3.4rc2
============================================================
x Avoid closing the customizer on arrow up key context
selection change (thanks barbaz for reporting)
x Prominently warn user whenever restrictions are disabled
x Support icon buttons elsewhere in the UI (e.g. in the
messagebox)
x Support for selectively hiding messages
x Support for extra UI in the popup's message box
x Prevent popup closure and automatic reload when
restrictions are disabled for the tab or globally
x Use a 5 seconds timeout to remotely fetch HTML events
source
x Better accessibility and styling for popup global buttons

[aarno]

Anyway, I would be all for a giant pop up box or some sort of warning tell me to not do this, as the cases for doing so are very few and far between for the majority of average users, I feel.

Done in latest development build, thanks:
v 11.3.4rc2
============================================================
x Avoid closing the customizer on arrow up key context
selection change (thanks barbaz for reporting)
x Prominently warn user whenever restrictions are disabled
x Support icon buttons elsewhere in the UI (e.g. in the
messagebox)
x Support for selectively hiding messages
x Support for extra UI in the popup's message box
x Prevent popup closure and automatic reload when
restrictions are disabled for the tab or globally
x Use a 5 seconds timeout to remotely fetch HTML events
source
x Better accessibility and styling for popup global buttons

Thank you so very much

It and your efforts are greatly appreciated

[aarno]

I also like to add that the "Drop to Hide" function is extremely helpful as well to assist in avoiding accidentally enabling the buttons of doom.

[ede]

I'm rather thinking of making it more obvious

I definitely second this idea. And there's two things I think would really be helpful:

• Unequalize the icons. Now they are "S+!" "BOX+!" "Clock+!" "Clock+(\)". I still have to hover them to know which one to press. Talking about mouse:hover…
• Straighten the text. "Disable restrictions globally". Both are negative expressions. "Unenable" "not allowed things". Minus multiplied with minus is plus, correct? But it's "allow everything" after all. Intuitivity rules in UI design (and consistence, but yeah). Just like it is for "trust everything on this site/page¹".

Btw, i'm still using the traditional design, the new one is hard to use.
________
¹ German interface here, so expressions may vary, maybe not even follow the same logic.