Change [Report Only] messages level

[BajoFondo]

Hi, Giorgio!

Maybe you can change the message level of your `[Report Only]` debug in Chrome to info or warning, better than error.

These messages appear by the hundreds, making it impossible to debug a web development project in Chromium. I'm an absolute fan of Fx, but there's no choice but to test that everything works in the most popular browser.

PS: I finally got through your spam filter, yesterday it was impossible for me to reply to this thread.

Noscript is interfering with Content Security Policy (CSP)

[barbaz]

Maybe you can change the message level of your `[Report Only]` debug in Chrome to info or warning, better than error.

Those messages look to be coming from Chromium, not NoScript, in which case NoScript wouldn't have control over them.

These messages appear by the hundreds, making it impossible to debug a web development project in Chromium.

I tried to filter them out with a regular expression, but couldn't get it to work. Not sure how Chromium devtools console is matching the regex against the messages?

Unless you're specifically testing how your site behaves in the presence of NoScript, it wouldn't be unreasonable to disable NoScript for web dev work (at least "Disable restrictions for this tab"). You trust the site that you are developing yourself, don't you?

PS: I finally got through your spam filter, yesterday it was impossible for me to reply to this thread.

Noscript is interfering with Content Security Policy (CSP)

Would you like this post merged with the other thread? I think it would be fine there, or fine to leave it here as a new thread if you prefer. Up to you

[BajoFondo]

Hi, barbaz.

Those messages look to be coming from Chromium, not NoScript, in which case NoScript wouldn't have control over them.

But until NS version 12 they did not appear. Can't do anything?

I tried to filter them out with a regular expression, but couldn't get it to work. Not sure how Chromium devtools console is matching the regex against the messages?

Unless you're specifically testing how your site behaves in the presence of NoScript, it wouldn't be unreasonable to disable NoScript for web dev work (at least "Disable restrictions for this tab"). You trust the site that you are developing yourself, don't you?

99.99% of the sites have Google Analytics, i want to stop tracking me. Never. Anyplace.

Would you like this post merged with the other thread? I think it would be fine there, or fine to leave it here as a new thread if you prefer. Up to you

Perhaps this thread has enough entity to remain independent, in case other users come with the same problem, don't you think?

Thanks!

[barbaz]

But until NS version 12 they did not appear. Can't do anything?

Previous versions of NoScript were using Manifest V2 extensions APIs. NoScript 12 is using Manifest V3 extensions APIs, which are more limited and as Giorgio said in the other thread it's not possible to keep the previous approach that didn't result in the messages.

99.99% of the sites have Google Analytics, i want to stop tracking me. Never. Anyplace.

The recommended solution is to have your sites respond to Global Privacy Control (and possibly also Do-Not-Track) and do not try to load Google Analytics or any other tracking if any of these signals are explicitly set to the "opt out" state.

If you are developing sites for someone else who will not allow you to respect user choice signals (boo!), note that NoScript is not the right tool for your case. NoScript is a security tool, not an anti-tracking tool. You might consider using a broader spectrum blocker such as uBlock Origin or using a dedicated tracker blocker.