noscript

noscript copied to clipboard

There are a few websites that have their own JS that I may want to allow to run when I'm on that website, but want to block when it's present in another website. For example, if I want to watch a Youtube video I may want to enable Youtube's JS (set it to trusted), but I don't necessarily want that JS running on any webpage that embeds a Youtube video. Even more directly, I've noticed that a lot of Google domains (e.g. often literally "google.com") are present all over, so I don't want this JS to run on random websites, but if I'm actually on a Google site then I do want it to run. I suggest adding a "trusted on this domain only" option alongside "unstrusted," "default," "temporarily trusted," and "trusted."

For example, if I want to watch a Youtube video I may want to enable Youtube's JS (set it to trusted)

Just wait a day. I have written a surrogate userscript that would allkw you to use YouTube without any their JS.

There are a few websites that have their own JS that I may want to allow to run when I'm on that website, but want to block when it's present in another website.

We need to integrate the features of noscript into umatrix and discard noscript.

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 already there, the UI may be ready by this summer.

@hackademix Is this going to be for both "trusted on this domain only" and "temporarily trusted on this domain only"?

@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 be a checkbox option inside the sub-panel for the CUSTOM setting (which you can configured either as TRUSTy or UNTRUSTy, temporary or permanent). In the NoScript options tab this won't be a checkbox but a domain selector, which you can use to switch between the CUSTOM settings for each domain, to configure or remove them.

Sounds great

@hackademix any update on this? not to rush you of course, I just wanted to know the current status, seeing as you said it might be done by summer...

@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 CSS PP0. I should be able to get back to it in October, and hopefully deliver by the end of the year.