Closed pauschuu closed 4 years ago
They are spoofed, the browser does not render them, it's uMatrix rendering them using span
tags.
In other words blocking scripts using uMatrix does not trigger the typical noscript behavior a browser would normally show? Hence the option is to restore the original noscript behavior.
So this is working as expected as I see it now. Closing the issue now.
Maybe link the "i" next to the Spoof <noscript> tags
to a documentation that clarifies this instead of linking it to the more general Mozilla Developer page. Meant as a humble suggestion.
Prerequisites
Description
Enabling the option
Spoof <noscript> tags
leads to a behaviour that one would expect when the option is disabled and vice versa.A specific URL where the issue occurs
https://www.faz.net/aktuell/ https://www.bild.de/ Sorry for these poor examples of press but those are sites where the problem occurs.
Steps to Reproduce
script
s for the example websitesSpoof <noscript> tags
for the example websitesSpoof <noscript> tags
for the example websitesRuleset
Basic rulesets:
Additional rulesets for testing:
Supporting evidence
Your environment
1.4.0
Google Chrome 83.0.4103.116 (Official Build) (64-bit) (But I remember that I had the same issue on Firefox too)
Windows 10.0.19041 Build 19041 (The issue was present when using my Arch Linux too)