It's way too hard to find out that NoScript blocked WebGL
Posted: Thu Aug 01, 2019 7:50 pm
If a WebGL is the only thing NoScript Webext blocks on a page, it is unnecessarily difficult to discover that NoScript is blocking something.
To reproduce:
1) remove WebGL from "Trusted" preset
2) load maps.google.com (with google.com set to Trusted)
Expected results: NoScript icon should report the blocked WebGL.
Actual results: NoScript icon is as if everything is allowed, but maps.google.com is missing a bunch of its UI.
WTH?? This is even worse than not reporting blocked "fetch"! I had to go through all the standard troubleshooting in safe mode etc to figure this out!!!!
If NoScript is blocking something, the toolbar icon should NOT be
with no blocked items count badge, period. The correct toolbar icon for this case would be 
(which I don't even see in the source code repo?).
Please restore the proper NoScript toolbar icon behavior as described in https://classic.noscript.net/features#basics, where the toolbar icon describes the state of ALL active content on the page. Thanks
To reproduce:
1) remove WebGL from "Trusted" preset
2) load maps.google.com (with google.com set to Trusted)
Expected results: NoScript icon should report the blocked WebGL.
Actual results: NoScript icon is as if everything is allowed, but maps.google.com is missing a bunch of its UI.
WTH?? This is even worse than not reporting blocked "fetch"! I had to go through all the standard troubleshooting in safe mode etc to figure this out!!!!
If NoScript is blocking something, the toolbar icon should NOT be
with no blocked items count badge, period. The correct toolbar icon for this case would be (which I don't even see in the source code repo?).Please restore the proper NoScript toolbar icon behavior as described in https://classic.noscript.net/features#basics, where the toolbar icon describes the state of ALL active content on the page. Thanks