InformAction Forums

I have noticed that "fetch" is a good addition to the CDN rules, since that allows page scripts to fetch content from the CDN, such as media files and streams, which does seem to be the usual case. frame, fetch and other are default choices for DEFAULT, so those should be good options. Per...

It happens again? The workaround should be still OK, as we don't really "select" the blank page in any way, we just stopped doing what was causing the bug. But if it's happening again, that means there is a new trigger for the bug. Cannot test myself as the newest FF has not yet landed on ...

I thought I explained them already. Click the "Disable restrictions globally" and "Disable restrictions for this tab" icons and you should find out yourself what the "new" icons are for.

Update: Turns out the problem is in the XSS filter. So if you absolutely need to be tracked by Facebook, you could disable XSS in the Options and then allow facebook.net. ;) @Giorgio: If you have not yet checked on this: The problematic call is to https://www.facebook.com/tr/ , which returns with so...

Both your Firefox and NoScript are bit old. Could you update them and see if the problem persists?

Can confirm the spike in cpu and ram usage (can cause whole OS to hang for a while) and crashing of Firefox. The culprit appears to be script from connect.facebook.net, so avoid allowing that domain until fix is found. For the facebook.net to appear in the popup, you need to enable: theguardian.com ...

If you do trust support.mozilla.com and wish to enable the scripts there, then everything is OK already. Like I said - NoScript cannot function on that site, meaning that it cannot block scripts there. So the scripts are running fine already.

support.mozilla.com is one of the restricted (extensions.webextensions.restrictedDomains) domains where NoScript cannot function due to design decision by Mozilla.

Unfortunately the message in the popup that should explain this is wrong. It is a known NoScript bug and hopefully will be fixed soon.

Oh no. I don't actually have any of them added. I just copied the list straight from the (NS10) sourcecode. So that is the default whitelist you should get on fresh install of NS10. But like you, I also deleted all the whitelisted sites way back when I was using NS5. Even though block_mozAddonManage...

Default TRUSTED sites (all permissions enabled): addons.mozilla.org afx.ms ajax.aspnetcdn.com ajax.googleapis.com bootstrapcdn.com code.jquery.com firstdata.com firstdata.lv gfx.ms google.com googlevideo.com gstatic.com hotmail.com live.com live.net maps.googleapis.com mozilla.net netflix.com nflxex...

That is odd, as I would imagine that the "script is undefined" error will surely lead to the condition... You don't need to enable script for default. The required domains are: twitch.tv twitchcdn.net twitchsvc.net (why does this trigger antispamfilter?) Though I did try it your way and st...

The bug is caused by some async functions getting executed in unexpected order, so there's no telling when it happens. To trigger the problem, you need to initially have webgl blocked for the twitch.tv. Refresh the page few times in attempt to trigger it. If you get "script undefined" erro...

Can confirm the problem. Sending fix suggestion to Giorgio. Not easy fix though.

Using Firefox 60 I do not notice anything out of place allowing scripts on those pages. Or is this FF52 only thing? Can you elaborate a bit on the steps necessary to reproduce the problem?

This is the same issue as discussed in https://forums.informaction.com/viewtopic.php?t=24944