New Gmail update causes mysterious snag...?

[onigami]

So, Gmail updated its UI in the last week or so. While accessing my email, Gmail does something funky now, in that the top of the page now has this message saying "Javascript must be enabled, etc. etc." as though to indicate that JS is disabled, with the rest of the page below it. Except JS isn't/shouldn't be disabled. NoScript is showing an icon saying the site is blocked, but opening it up, it says both the sites it's getting scripts from are trusted, so it shouldn't be popping up like this.

Here's a screenshot of the top of the page (right click to view full image, I tried linking it but I got hit with an anti-spam block):


What gives? Something strange is going on...

(Note that while ABP is enabled in that screenshot, I get the same effect when it's disabled)

[barbaz]

What version of NoScript?
How have you determined that NoScript is what's disabling JS?

BTW, your screenshot looks like you have both Adblock Plus and uBlock Origin. Installing/using multiple adblock type extensions concurrently is known to be problematic. Best pick only one of them to keep, transferring filters if necessary.

[GunSmoke]

Try clearing "XSS choices".
I'm on NoScript V. 10.1.8.23 and that worked for me.

[therube]

I'll note the sites are in red, if that matters.

Do you have an antivirus that may be interfering?

[Giorgio Maone]

Please check latest development build, thanks:
v 10.1.8.9rc1
=============================================================
+ Completely revamped CSP backend, enforcing policies both in
webRequest and in the DOM
- removed obsoleted failsafes, including forced reloads
x [Build] Better support for versions bumps
x Updated TLDs
x [Build] Improved TLD auto-updater

[aberrometer]

For what it's worth, I had the same problem, and updating to the development version fixed it.

But of course I forgot to check what version I had before updating, so can't help you with that...

[billdehaan]

Please check latest development build, thanks:
v 10.1.8.9rc1

Just to chip in, I've experienced the exact same problem with 1.8.23 (the most recent version from the Firefox addons site) since Saturday. I traced it down to NoScript being the extension that triggered it, and came here looking for answers. I just updated to 1.8.9rc1 as per the above, and the problem appears to have been resolved. Many thanks.

Of course, looking at the Firefox site, I now see that the formal 1.8.9 has been released, as of two hours ago as I write this, and I can confirm that it also addresses the issue.