uBlockOrigin / uMatrix-issues

This is the community-maintained issue tracker for uMatrix
https://github.com/gorhill/uMatrix
123 stars 17 forks source link

"Spoof <noscript> tags" works inverse #272

Closed pauschuu closed 4 years ago

pauschuu commented 4 years ago

Prerequisites

Description

umatrix_spoof-noscript-disabled_faz umatrix_spoof-noscript-enabled_faz

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

  1. Disable at least scripts for the example websites
  2. Enable Spoof <noscript> tags for the example websites
  3. The websites will show an overlay which is triggered by their noscript tag
  4. Disable Spoof <noscript> tags for the example websites
  5. The websites will show their normal contents

Ruleset

Basic rulesets:

https-strict: behind-the-scene false
matrix-off: about-scheme true
matrix-off: behind-the-scene true
matrix-off: chrome-extension-scheme true
matrix-off: chrome-scheme true
matrix-off: moz-extension-scheme true
matrix-off: opera-scheme true
matrix-off: vivaldi-scheme true
matrix-off: wyciwyg-scheme true
noscript-spoof: * true
referrer-spoof: * true
referrer-spoof: behind-the-scene false
* * * block
* * cookie block
* 1st-party css allow
* 1st-party image allow

Additional rulesets for testing:

noscript-spoof: bild.de false
noscript-spoof: faz.net false

Supporting evidence

Your environment

gorhill commented 4 years ago

They are spoofed, the browser does not render them, it's uMatrix rendering them using span tags.

pauschuu commented 4 years ago

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.