noscript
noscript copied to clipboard
hackademix
noscript + firefox containers
Is there a way to block a domain in all tabs except one specific container Firefox container? That way, I could have a Youtube container with google scripts activated, and finally ditch chromium.
I came here to suggest this too. For example, I'd like to allow scripts from twitter.com but only when I'm in the permanent container I use for accessing Twitter.
Although I suppose if I could say "*.twitter.com and *.twimg.com should be Trusted but only when the tab URL is at *.twitter.com", that would do the same thing for every use case I can think of, without requiring noscript to know anything about containers. @mfr-itr, what do you think of that alternative?
Hum, did not know that was possible. At first glance it seems good enough, not sure if it would be sufficient though... Edit: my bad, I thought you meant it was possible right now.
I'm pretty sure that that kind of thing is technically possible under the hood, although the UI might not fully support it.
I would love to see container support similar to Cookie AutoDelete's one - it currently allows to setup cookie retention policies based on the used Firefox container. Implemented pretty straight forward by selecting different configuration stores based on the tab's container context, here on GitHub.
although the UI might not fully support it.
Why would this require UI changes?
I'd be happy if all site permissions were "namespaced" within Firefox containers. Each container can have a different set of settings, and there is IMO no need to change the UI.
Yes please this would be awsome. Cookie Autodelete already has this feature
There’s a contextualIdentities API, but I don’t find any way to query the container of a particular tab. Even worse, if NoScript asks for permission to access containers, Firefox will enable containers even if they would be disabled otherwise. This forces users to use a feature that they don’t need, which is bad user experience (mysterious menu options, maybe also a small but non-zero runtime cost). Probably NoScript is popular enough to convince Mozilla to provide a solution that covers our use case?
