InformAction Forums

Setting the following three domains as Trusted and I'm able to create new threads and comment others.

suomi24.fi
google.com
gstatic.com

You seem to have these set to Custom. I recommend you check that you have all the necessary permissions set for them.

Good to hear you got it working. adnxs.com is definitely a tracking domain. Not much info on olsvc.com, but it is apparently owned by Microsoft. Quite unfortunate if they require tracking scripts for login. Can't find any previous reports that either of these would be required but that doesn't mean ...

Try allowing office365.com and azureedge.net too. If you can't find them in the list, go to (NoScript Options -> Per-site Permissions) and add them there (click the red lock icons to change them to green). However I'm pretty sure this has nothing to do with the Costco problem. Separating this to its...

Instead of outlook.live.com, I need to allow login.live.com. And msauth.net on top of that.

Though it might be best just to allow whole live.com so you are less likely to run into any additional problems.

@Bencyc: Can you copypaste the error message you get or screenshot it?

Going to https://login.live.com/ I get the regular "Cant use this site with javascript disabled!" error message.

What url are you using when you get the error?

Here's what happens to me: Javascript enabled: https://www.costco.com/laptops.html loads fine the first time and any subsequent reloads. Javascript disabled (either with NoScript or through about:config): First time open (cookies and cache cleared) - site loads fine (seems blank but the content is t...

There is no link - wrote it myself. Here: // ==UserScript== // @name Google Redirect Removal // @version 1 // @license Public Domain // @include *://*.google.com/* // @grant none // ==/UserScript== // Remove google.com redirect from the links. for(let i = 0; i < document.links.length; i++) { let lin...

It would appear changing useragent helps here too (like with google search). Unfortunately the old way to change useragent on FireFox does not work anymore (https://forums.informaction.com/viewtopic.php?f=7&t=25573&sid=1fbfa725350602e852419e5b66df3265&start=45#p101612). Quoting myself: First of all,...

I did note that current FF (Quantum) would need an extension to spoof the UA (on a per site basis). I did notice but felt the need to highlight it. Took me by surprise when I found out about it only few days ago. I use a little Greasemonkey script to remove the "https://www.google.com/url?q=..." re...

@asaone7: At least you are more free to toy around with the useragents. Not that it seems to be of any help in this case... @sprocketoctopus: Any style changes done in the Inspect Element or Console are reset every time you refresh or go to another page. But like barbaz said, you could use Stylus to...

First of all, since FF71, site specific settings (general.useragent.override.somesite.com) do not work anymore. The pref has been removed. Also note that general.useragent.override (global useragent change) has no effect if privacy.resistFingerprinting is enabled. The official way to change useragen...

I have tested few useragent strings but none of them seem to bring back the old search. There might be other ways, but I have no clue what those might be. You could always send feedback to Google and urge them to enable the old search interface for those that disable scripting. Personally I switched...

It looks like the EverSyncs options page tries to load several external scripts from https://everhelper.me NoScript does not block internal pages, but it does block external scripts. Unfortunately this does not show up in the popup. If you trust https://everhelper.me, you could navigate to the page ...

The loss of elements is quite natural when you disable scripting.

Unfortunately there is currently no way to disable the automatic refreshing. I too wish there was.

Only way to prevent the refresh from happening is to not change the permissions before you want them applied.

So looks like I overlooked some cases (such as the session restore) with the file- and ftp-protocol. Also found it interesting that using the async call like that actually worked. So it appears that the xmlhttprequest is not quite so synchronous in every case after all. Armed with that knowledge, he...