InformAction Forums

I depend on NoScript, but I'll admit I've not attempted to understand all of it's nuances. The way I normally use it is I go to a page I know, then click on the "disable restrictions on this tab" if I need to allow scripts. When a tab first opens, it prevents scripts from running, until or unless I disable restrictions.

A few days ago disabling restrictions still stopped some scripts, which cripples some of the sites I go to (including my own web pages). When I select disable restrictions on this tab the page reloads and the NoScript icon on the top of Chrome says 1 or more scripts are still restricted. The only way I can get these sites to work right is to disable globally, which of course is not what I want to do. I can't remember exactly when this started, but I think it was sometime yesterday (Sunday, 5-Oct) or maybe late Saturday (4-Oct).

I don't think I changed anything, but it wouldn't surprise me to find out I did.

Anyone have an idea of what I need to do to get NoScript back working as expected?

Sorry, I thought I was logged in when I posted the above. Anyway, I'm the poster.

Horsefly

What version of NoScript?

Example web pages that fail load properly?
If on those pages, instead of disable on this tab, if you allow globally, does that make a difference?

Confirmed. Fixed in latest development build:
v 11.1.1rc1
============================================================
x Updated TLDs
x Better heuristic to figure out missing data while
computing contextual policies
x Fixed regression breaking per-tab restrictions disablement
(thanks Horsefly for report)

Unfortunately you may need wait some hours for an 11.1.1 update to be published on the Chrome Store because of the review process (I'm not sure if you can temporarily downgrade, though).

Awesome! Thanks Giorgio!

I thought I was going crazy. Good to see it's been fixed. I can wait for it to migrate through the Chrome process.