InformAction Forums

I have a synology disk station and set its local address to trusted.
The tooltip still shows 2/4 items blocked and I can't find a way to disable any blocking.
Where can I see what is still blocked and how can I trust all my local addresses?

Are you sure the tooltip and icon are correct? How do you know something is actually blocked by NoScript?

I actually don't know if anything is blocked, I just noticed the icon showing '2' blocked items.
If I hover over the icon the tooltip comes up and shows what can be seen on the picture.

If I click on the icon I get the list which shows the two trusted entries but no blocked entry.
The whole thing is repeatable, i. e. if I close the tab and re-open it, the problem re-appears.
This is very confusing.

Is every capability enabled in your TRUSTED preset?
However, I've got a Synology NAS myself and I think I understand what's happening there: the page delivers its own Content Security Policy, which is in conflict with some element of the UI (at least in my case, an inline script inserted by prototype.js, but in your case it might be even more stuff since it seems you're using some kaspersky extension which inserts its own scripts everywhere) and blocks it. The CSP violation event then gets intercepted by NoScript, which cannot tell the blocking CSP is not its own and reports the blockage.
I'm currently investigating whether there's actually some way to discriminate: I think it's possible on Chrome, which IIRC lets you detect invalid CSP directives in the violation reports and therefore allows marking and telling apart NoScript's CSP; this didn't work on Firefox last time I checked, though.

Thanks for the explanation.
Yes every capability is enabled for trusted sites.

So far I did not experience any problems in the functionality of the synology GUI.
It's just irritating that noscript shows that something is blocked although everything is set as trusted.

BTW, it should be much better in latest development build, thanks.
v 11.1.6rc3
============================================================
x More accurate blockage reporting, with better filtering of
page's own CSP effects

You're great!
I updated to 11.1.6rc3 and the problem is gone.