InformAction Forums

Facebook will not load properly when the new version of NoScript is enabled. Only the top toolbar loads, but no buttons work. NoScript only shows facebook.com and fbcdn.net (both trusted), although I have the other domains allowed in preferences (facebook.net, fbsbx.net, fbstatic-a.akamaihd.net) Most frustratingly, the "temporarily allow all this page" button doesn't help either. It only loads properly if I disable the add-on entirely.

Same here. Everything on FB trusted, just the top bar shows. Weirdness. I miss the old NS, all that muscle memory is now useless. I keep checking back and will update as newer versions come out and try it again, but so far I can't use the thing, leaving it disabled.

ariston72 wrote:Facebook will not load properly when the new version of NoScript is enabled. Only the top toolbar loads, but no buttons work. NoScript only shows facebook.com and fbcdn.net (both trusted), although I have the other domains allowed in preferences (facebook.net, fbsbx.net, fbstatic-a.akamaihd.net) Most frustratingly, the "temporarily allow all this page" button doesn't help either. It only loads properly if I disable the add-on entirely.

Just checked FB and it worked fine with me. Have you already looked up the Trusted Tab's settings (click on the tab)? Are there any boxes that aren't ticked off yet that might block certain items or prevent them from working?

If it looks like this (here, it's the Custom tab, Trusted looks the same),


you may want to check all boxes to see if FB runs as supposed.

That got it! For some reason, under the "trusted" tab, the sites had "script" selected buy grayed out. I had to switch each domain to "custom" and manually check "script" on each one (everything else was already checked). Still not sure why "temporarily allow all this page" wouldn't work... Anyway, thanks for the help!
I don't know why the NoScript icon doesn't list all domains on the site, like it used to. I tried the same solution on this site, and it still doesn't show the captcha prompt on this page. Still having to disable NS to post this comment. :-/

ariston72 wrote:That got it! For some reason, under the "trusted" tab, the sites had "script" selected buy grayed out. I had to switch each domain to "custom" and manually check "script" on each one (everything else was already checked). Still not sure why "temporarily allow all this page" wouldn't work... Anyway, thanks for the help!
I don't know why the NoScript icon doesn't list all domains on the site, like it used to. I tried the same solution on this site, and it still doesn't show the captcha prompt on this page. Still having to disable NS to post this comment. :-/

The selected grayed out options SHOULD mean "This is the "trusted" setting, which means scripts are allowed, no you can't take that back".

Similarly in the "untrusted" setting the box is unchecked and greyed out, meaning "no dude, you can't allow scripts in the "untrusted" setting, that's why it's called "untrusted".

Moving it to custom with the same check-marks set as in trusted shouldn't make a difference.

My guess is that at the core there is an issue with how NS10 took the old rules from NS5, meaning that for rules you didn't SET in NS10, what it shows is sometimes not what it does.
NS10 only sets it's own rules when you change the settings IN NS10, so I guess by moving all of them to custom you overwrote the faulty NS5 rules.

ariston72 wrote:That got it! For some reason, under the "trusted" tab, the sites had "script" selected buy grayed out. I had to switch each domain to "custom" and manually check "script" on each one (everything else was already checked). Still not sure why "temporarily allow all this page" wouldn't work... Anyway, thanks for the help!

I believe the issue is with the Custom tab since it seems to affect Trusted (at least in the older 10.1.1 version) and vice versa. Did you use the latest 10.1.2 update and/or did you use Custom in the first place?
Because in its newest release, Trusted (and also Default) seems to overwrite all Custom settings. So, changes you made in Custom will be reverted by Trusted and Default, meaning if you untick certain boxes under Custom, Trusted will reset those to all-ticked and Default to unticked.

Maybe in the future, Custom will be totally independent from all the other tabs which would make more sense as it is the Custom option (that should be handled differently).

ariston72 wrote: I don't know why the NoScript icon doesn't list all domains on the site, like it used to. I tried the same solution on this site, and it still doesn't show the captcha prompt on this page. Still having to disable NS to post this comment. :-/

Just cross-check whether Trusted and Custom have the same boxes checked just to rule out any inteference that might still occur. Then go back to Trusted (and maybe set the padlock to red (not needed since both use https but still to be sure nothing is hindering your settings) and it should behave normally. If NS via checkboxes wasn't allowed to load scripts, it would then show just the master domains and not third party domains. For this site, you should see informaction.com in Default (no boxes ticked = all scripts and items supressed) and, when set to Trusted, you should also see google.com as domains. You need to set those two to Trusted and the Captcha should appear again. Make sure you didn't deny Google scripts.

Oh, and maybe it would be also wise to review your domain list in options. I just experienced that and older entry for Youtube wasn't affect by the web-extension settings I changed. I just deleted this older one inside the list by setting it to Default to make it disappear. Then I went back to YT and set it back to Trusted, and voilá, all the settings I change in the extension will also be transferred to the whitelist entry. Maybe this caused some of your troubles.

NoScriptian wrote:Trusted (and also Default) seems to overwrite all Custom settings. So, changes you made in Custom will be reverted by Trusted and Default, meaning if you untick certain boxes under Custom, Trusted will reset those to all-ticked and Default to unticked.

Maybe in the future, Custom will be totally independent from all the other tabs which would make more sense as it is the Custom option (that should be handled differently)..

No, this is correct behavior. Because Custom is not like the other three. Default, Trusted, and Untrusted are partially-configurable presets. Custom is not a preset. It allows you to fine-tune permissions for THAT SPECIFIC SITE.

The current UI makes this point very confusing. Really, configuring Default/Trusted/Untrusted should be moved out into some sort of "global options", and only Custom should be configurable under the 'current' site (as it is now).

NoScriptian wrote:
I believe the issue is with the Custom tab since it seems to affect Trusted (at least in the older 10.1.1 version) and vice versa. Did you use the latest 10.1.2 update and/or did you use Custom in the first place?
Because in its newest release, Trusted (and also Default) seems to overwrite all Custom settings. So, changes you made in Custom will be reverted by Trusted and Default, meaning if you untick certain boxes under Custom, Trusted will reset those to all-ticked and Default to unticked.

Maybe in the future, Custom will be totally independent from all the other tabs which would make more sense as it is the Custom option (that should be handled differently).

That's not exactly what is happening. (keep an eye on the debug log to see why). And you have a logical inversion in there.

Yes, if you switch from Custom to any other preset, NS basically forgets what you HAD as custom.
(in the log it removes the entire custom entry for that source, and puts the source back in the place of said preset)
Meaning if you then put it back TO custom, it works with those checkmarks from where you moved it from again. (if you move something from trusted to custom, it uses the checks from trusted) Which you then customize.
If you look at the debug log, you kind of see why this is expected behavior, I don't think there is a reasonable "save deactivated custom rules" syntax in there, it has to remove the custom rule when you move something away from custom to avoid double entries.
Equally, if you move something to "default" from anywhere, it removes the whole source out of the config entirely, since there is no "this is in the default set" rule. Everything that is not in trusted, untrusted or has it's own custom rule gets the "default" rules applied. NS doesn't remember which sources those are.

I believe the issue is with the Custom tab since it seems to affect Trusted (at least in the older 10.1.1 version)

That is different (the other way around basically), and I don't think it did. Custom and default were connected, as if there was no custom at all. But that is in the past and was a bug.

Currently if you look at the log it basically has 6 major areas.
Rules for default
Rules for untrusted
rules for trusted
Members of untrusted
Members of trusted
Members of custom with individual rules each.

If the behaviour changed by moving something from trusted to custom but explicitly the same rules as the trusted set, somehow the initial entry must have been faulty, potentially when it was imported from NS5.

The thing is due to the way it captures (or doesn't) subdomains currently (unless you put them all in manually) I mostly run EVERYTHING in default, selectively moving to trusted and temp trusted set to everything allowed. I have yet to see something not work when it should, I rather have the problem of not being able to be as specific as I'd like without parsing sourcecode and manual entries.

Thank you both for pointing that out. But for me, it is a confusing behavior as I would think Custom is a seperate option, indepent of the others. I don't want this to be altered by Default or Trusted just because it is a setting I'd like to handle myself. I do understand that Trusted and Default are master templates for all websites and Custom is specific to just a particular site. But because that is the case, I don't want those options to overwrite my Custom settings which would cause me to have to start all over again.

Pansa wrote: If you look at the debug log, you kind of see why this is expected behavior, I don't think there is a reasonable "save deactivated custom rules" syntax in there, it has to remove the custom rule when you move something away from custom to avoid double entries.

I'm no programmer but wouldn't it be possible to just tell NS which option and specific settings is used right now? Custom--> look up checkmarks there Default-->lookup checkmarks there without having these two "cross-talking" to each other?

NoScriptian wrote:
I'm no programmer but wouldn't it be possible to just tell NS which option and specific settings is used right now? Custom--> look up checkmarks there Default-->lookup checkmarks there without having these two "cross-talking" to each other?

It does exactly that for the true presets.
But there is no "custom" preset. Custom creates a rule for each source.

as long as the source is set to custom that is what happens. But if you move a source out of custom, it doesn't keep the custom settings for a source not in custom any more.

The problem is the "over there" for custom is defined by the source name that NS is looking up in the first place. If you remove it there, so NS doesn't think the custom ruleset applies at this moment, all that would be left are a set of rules that did only apply to that page, with no one knowing who that applied to.

In a way that is what custom means, a bunch of individual rules. Compared with trusted and untrusted which means "this is a list of pages that all use the same rules that are written -> yonder".

Thank you both for pointing that out. But for me, it is a confusing behavior as I would think Custom is a seperate option, indepent of the others. I don't want this to be altered by Default or Trusted just because it is a setting I'd like to handle myself. I do understand that Trusted and Default are master templates for all websites and Custom is specific to just a particular site. But because that is the case, I don't want those options to overwrite my Custom settings which would cause me to have to start all over again.

They don't overwrite your custom settings.
What you want is something that I personally dreaded was going on in 10.1.1 which was a bug.

To me custom doesn't mean "one set of rules" it means "very specifically what I want for THIS page, but not for others, even others that I also customize"
I specifically want every page in custom to have their own set of rules, even from each other.

I guess in a sense ultimately you could program a specific separate behaviour for custom rules were it "still remembers" the last custom ruleset for each page even though it currently doesn't apply and instead forgetting them.
But that is a very specific and not really intended way of doing things, blowing up the config and requireing you to still always check whether the custom rules for that page were the ones you remembered.

If you carefully crafted the custom rules for a source, if you want to change things further, you can give the permissions to that custom ruleset and remove them later.
And its 8 checkmarks the number of meaningful combinations is somewhat limited. You shouldn't want to move custom to trusted and back constantly anyway.

Thanks, I think I'm starting to understand the rationale behind it.

I had this same problem - Facebook would only load partially, and nothing would work (couldn't open my notfications, mouse-over wouldn't produce pop-ups), despite having marked facebook.com and fbcdn.net as Trusted. I only managed to get it to work by selecting Custom for facebook.com and checking all the boxes. But why is that different from simply marking it as Trusted?

Callum wrote:I had this same problem - Facebook would only load partially, and nothing would work (couldn't open my notfications, mouse-over wouldn't produce pop-ups), despite having marked facebook.com and fbcdn.net as Trusted. I only managed to get it to work by selecting Custom for facebook.com and checking all the boxes. But why is that different from simply marking it as Trusted?

Because NoScript 10.1.3c2 had a serious bug. If you upgrade to 10.1.3c3 or later, you should be able to select Trusted and check all the boxes, and this will apply to all Trusted sites.