"Disable restrictions for this tab" doesn't work as expected under easily reproducible conditions. about noscript HOT 5 CLOSED

I have tested older releases to see when the bug was introduced. The last release where "Disable restrictions for this tab" worked as expected was NoScript 10.1.9.8 (Oct 6, 2018) and the first one with the bug was NoScript 10.1.9.9rc1 (Oct 13, 2018). I think this should help you find the bug.

from noscript.

The problem is with the cookie-based hack to communicate per-tab information, which cannot work with non-HTTP subframes (such the about:blank ones in your test page). The dev tools and other extension seem to lock the frame loading so that the inherited cookie is read before it gets erased by the parent page, but this doesn't happen (nor is actually desirable) in normal conditions.
Also, the "old" name-based hack is not affected by this problem, but had serious issues of its own.
I'm afraid I must resort to yet some other sort of hack, possibly for subframes only...

from noscript.

Thanks for looking into the problem and your interesting analysis!

I thought about using NoScript as my only extension again and the behavior confused me quite a bit. This function is very convenient for me in certain situations, but at the end of the day the most important thing for me is to be sure that unwanted scripts are not executed.

Feel free to let me know, if I can test anything.

from noscript.

Please check https://github.com/hackademix/noscript/releases/tag/10.2.2rc1, thanks.

from noscript.

Works like a charm for the test page and I have not seen any negative surprises so far. Thanks for the fix!

from noscript.