Giorgio Maone
Giorgio Maone
The problem is that the only way a webextension can disable JavaScript is by using Content Security Policies. CSP don't affect `` elements rendering, which are therefore kept hidden by...
It's working here, 3 tabs with 3 different GMail accounts all open. What browser are you using? Which NoScript version? Could you share your NoScript Options>Export file? Thanks.
> I suggest adding a "trusted on this domain only" option alongside "unstrusted," "default," "temporarily trusted," and "trusted." Contextual permissions are actually planned and work is undergoing: the back-end is...
> @hackademix Is this going to be for both "trusted on this domain only" and "temporarily trusted on this domain only"? "For this domain only" in the popup is gonna...
> @hackademix any update on this? I had to delay the work on this a bit because of overlapping projects involving the NoScript Commons Library, JShelter (AKA JS Restrictor) and...
If you mean the "noscript" capability, it allows the page to render its HTML noscript fallback content, see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/noscript
Are there any other popular/recommended extensions around implementing dark-mode, as a template to follow? (just checked uBlock and HTTPS Everywhere, they don't).
@KOLANICH is right on this. However, if for some reason you really need a lower level not blocking those 3rd party requests (which for Firefox users are usually filtered out...
Yes, I confirm disabling all restrictions means **all**, including those implied from the UNTRUSTED preset, and yes, an option like "Enforce the UNTRUSTED preset even when restrictions are disabled globally...
You just need to set stackexchange.com and ssstatic.com to TRUSTED. If you want your permissions to be more fine-grained, `NoScript Options>Appearance>List full addresses in the permissions popup (https://www.noscript.net)`, then set...