InformAction Forums

Nothing has changed in my Firefox browser other than I noticed NoScript updated last night. Now when I go to Newser's comment section which uses Disqus comments it won't load. It does load if I disable NoScript though.
Can someone help?

Which version? 11.0.35 or .36?

Version 11.0.35

I am experiencing the same odd behaviors since the update 11.0.35.

This is not a common thing - pretty much all other pages work fine.
When it does happen, the page fails to load at all, with NoScript stating "1/1 blocked" citing "<script>" as the target.

And that happens even if:
-The page in question is trusted
-The tab restrictions are temporarily lifted
-All NoScript restrictions are temporarily lifted

The only way to restore the page is to disable NoScript in the Extension settings.


I've seen this most recently on https://app.slack.com/client/
With the FF Dev edition (80.0b4) I've also seen https://outlook.office365.com/mail/inbox/ break.

I've added screenshots of the issue in action on Slack here:
https://imgur.com/a/UWU3kyw

I am running Firefox 79.0 64-bit (default install) on Windows 10 64-Bit Enterprise version 1909 with all updates installed.
The FF install is about 24hrs old on a brand new profile.
Other addons active are:
-uBlock Origin
-PrivacyBadger
-Cookie QuickManager
-Disconnect

Disabling the other addons does not affect the page breaking. It can be narrowed down to noScript.


Update:
I've seen the issue crop up and then go away for pages, e.g. Slack now works again, GoogleDocs went blank with the same issue until I opened it in a new window (https://docs.google.com/document/).
Now GoogleDocs is working again and Slack went back to blank. No changes in config etc. Just pressing refresh

It's very difficult to reproduce consistently. Armchair-QA'ing, I would say that this seems to be an issue with the state of the plugin itself, perhaps a memory issue or state issue?

Please check latest RC version, thanks:

v 11.0.37rc1
============================================================
x Updated TLDs
x sendSyncMessage support for multiple suspension requests
(should fix extension script injection issues)

Thanks, Giorgio! That seems to have fixed it cause the pages appear to be working normally again with it enabled.

Thanks, I had the same issue and v 11.0.37rc1 fixed it for me.

So far, problematic pages are now working! Awesome!!

I'll give this a bit of a longer test, as the issue was something that would come and go.
And I don't want to declare victory too early.

Thanks Giorgio!!

I am experiencing a new issue: The NoScript menu does not expand on first click.
I believe this was also present with the previous, non-RC version.

NoScript Version: 11.0.37rc1
FireFox / Windows unchanged from yesterday.


Steps to reproduce:
1. Navigate to a page
2. Wait for page to load
3. Click the NoScript icon in the toolbar
4. On the first click, the menu will not expand. The little "down" / "expand" arrow will be shown, but no box with options will be chosen.
5. On the second click, it will work as intended.
6. On the third click, the menu will not pop up again
7. On the fourth click, menu will work as intended
8. ....

See screenshots here:
https://imgur.com/a/Dlxg9VY

Occasionally, the menu opens up as a separate window.
I've been able to cause the window to pop up consistently by rapidly (double-)clicking the NoScript menu icon.

There seems to be a problem with a toggle or a state that flipped, as the issue is coming and going consistently.


I've seen this on pretty much all pages, including this Forum (posting.php?mode=reply&f=7&t=26068). Mmmmh.

Edit: Grammar.

mseul wrote: ↑Sat Aug 08, 2020 3:31 pm 4. On the first click, the menu will not expand. The little "down" / "expand" arrow will be shown,

If you just wait a bit, does the popup eventually load?

No.
I've waited for 30 seconds and the box does not show up.

If I click a second time it is displayed almost immediately.
It seems not to be an issue of slow loading but rather not loading at all.

I am not experiencing this issue with any other plugin that emits a similar popup UI, e.g. PrivacyBadger or uBlock Origin.
Those might occasionally be chugging a bit if the page contains a lot of elements to process, but all load consistently.

From looking at how the plugin is (not) rendered, I'm wondering if it is a Z-Layer display issue.
In that the popup actually is rendered, but is hidden behind other parts of the browser UI / "Chrome".


What is also notable, is that the "down arrow" is rendered white, following the plugin's styling, if the popup shows, while staying dark/grey, following the browser's style, if it is not rendered.
I am using the "Dark" theme that comes with the browser, not a custom theme.

See my screenshots from earlier, note how the arrow looks different: https://imgur.com/a/Dlxg9VY

The NoScript menu does not expand on first click.

I've seen that too - more recently.
(Haven't paid attention to 2nd or 3rd clicks or anything like that, as I don't expect much, & pretty much take what comes [or not].)

Occasionally, the menu opens up as a separate window.

The modal issue has been around for a long while now.
(And probably affects all extensions.
And likely is just piss poor implementation of <everything> by Quantum.
Likely to occur anytime Quantum is under relatively high "load".
[First item, above, likely exacerbated by high load in Quantum too.])

rather not loading at all

That, is different from what I've been seeing.

I've done a bit more testing and this seems to be a browser-state problem.


- Stay in browser session where issue occurs
- Disable all other extensions other than NoScript
- Test page -> issue persists
- Refresh page -> Issue persists

Then...
- Close browser, keep all plugins except Noscript disable
- Test page -> issue gone
- Refresh page -> issue gone

Then...
- Enable all plugins
- Test page -> issue gone
- Refresh page -> Issue gone


I'm almost willing to assert that the issue seems to be within the plugin itself in that it will enter a "Break" state, where it will exhibit these issues.
I'll be checking also with a separate, clean profile that only contains NoScript if I can reproduce this issue.

And, just to fully acknowledge that, I do use quite a few privacy plugins, so there is of course the chance that NoScript is suffering from another plugin misbehaving. So, if I am the only one seeing these things and it's not reproducible, it may very well be a me-problem.

I've seen multiple issues since recent update.

1) Slack not loading -- I disabled NoScript over the weekend to work around it, and now today it is working.
2) Office365 Outlook + Calendar not loading -- I disabled NoScript over the weekend to work around it, and now today it is working.
3) Now my local web app not loading -- I didn't change anything of my app code, and if I disable NoScript, it works again.

So in troubleshooting the last case, it seems to be an issue with SCRIPT tag loading order.

For example, I have a mix of:

a) HEAD > SCRIPT
b) BODY > SCRIPT TYPE="MODULE" SRC="..."
c) BODY > SCRIPT TYPE="MODULE" (an inline script)

Normally, even if (b) and (c) were loaded in parallel, and they finished downloading in random order, they would still be executed in the order that they appear in the source.

However, when NOSCRIPT is loaded, I now see a bunch of debug output in the console about `sendSyncMessage running deferred` (seems new since latest extension update) AND I observe that the execution order is not respected for the inline scripts (case (c) above). The inline scripts seem to execute immediately, even though the scripts before them have not finished loading or executing yet.

This causes errors for me because I have global window variables declared by (b) which are later referenced by (c).

My experience with NoScript causing trouble on various sites over the past two weeks has led me to assume that something fundamental has changed in the extension, and it is probably breaking a lot of sites. This has caused me to question the quality of work and whether I should continue to trust the extension or look for simpler, more reliable alternatives. For now I will just leave the extension disabled and wait, but please fix ASAP.

This thread has become a hopeless mess of too many different problems, locking.

guest812, your post is so unlike anything else reported in this thread that I've split it to a separate thread so you can get proper attention.