InformAction Forums

Hello, all. There's a weird problem I started noticing a couple of days ago... When Firefox starts it opens many session tabs that I use daily, and they usually get reloaded when switching to that tab (controlled by FF setting "Don't load tabs until selected"). Despite the NoScript setting "Temporarily allow top level sites by default", the given site does NOT appear among the whitelisted pages in italics, which would signify temporary allowance, and therefore it has JS disabled. The site does appear there if I manually hit "reload". it might be a misconfiguration on my part, I'm not sure. I tried resetting NoScript settings to defaults, and then restoring my few custom settings one by one, hoping it would fix the problem, but no.

Also, when I open a new empty tab and type some webpage's address it isn't temporarily allowed either.

You aren't the first one reporting weirdness with session restore on Iceweasel 31.x: viewtopic.php?f=10&t=20901

Can you reproduce the problem on a clean profile with only NoScript installed, and all defaults except for checking "Temporarily allow top-level sites by default"?
Can you reproduce the problem on Firefox/Iceweasel 38.x ?

rihad wrote:Also, when I open a new empty tab and type some webpage's address it isn't temporarily allowed either.

With what new tab page? Default or custom?

Just about any page, hit Ctrl+T and type in any site's address you haven't opened during this session and that you're sure has some kind of scripting on. The NoScript icon will be displayed as "redded out". The site isn't added to whitelisted pages. Wait for the page to load completely and simply hit reload, the NS icon will now be a plain blue "S", and the page gets added as whitelisted.

Unfortunately 31.7.0 is whatever Debian stable currently has and will have as per their policy. I could pull in a newer FF out from the testing branch if the problem persists.

As for the addons, the most pertinent would be TMP, but again I've been noticing the problem for only a few days. I haven't installed new plugins/extensions for a long time... just what is necessary to keep the ball rolling.

Well, if you haven't made many changes, maybe a new profile isn't the first thing to try.
Do you have your addons set to auto update? Assuming so:
1) disable all but NoScript and see if the problem persists. If so there may be a bug in NoScript... then please try the clean profile test mentioned above.
2) If the problem does not persist, the issue is likely not a NoScript bug, but one of the addons you disabled. Enable them one at a time, until you get the issue. Then enable all addons but the suspect, to confirm that it's the problem.

The Browser Console (Ctrl-Shift-J) might have a hint if it is an extension conflict.

If you don't have your addons set to auto update, do you remember what addon(s) you updated last before this problem started?

rihad wrote:Unfortunately 31.7.0 is whatever Debian stable currently has and will have as per their policy. I could pull in a newer FF out from the testing branch if the problem persists.

This would be helpful for testing, but NoScript supports Firefox 3.0.9 and later (and corresponding Iceweasel versions), so while this may fix the problem for you, there's still a problem with some supported browsers...

As you suggested, I just disabled ALL addons except for NoScript. Still exactly the same problem: neither session-restored tabs nor new pages opened in a new tab (Ctrl+T) are added to the "temporarily allowed" whitelist. Only a page reload fixes the problem. Some boards (like Invision power board) even detect that JS has been disabled and tell it to you:

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

A simple page refresh makes the message go away.

Please try:
1) clean profile test as suggested above
2) if it is *not* reproducible there, what if you then import your entire NS config into the clean profile using the Import and Export buttons *on the very bottom* of NS Options?

Thanks. Creating a clean profile isn't as scary as it sounded I created a new profile (by running firefox -profilemanager) without affecting the default profile, and installed NoScript into a pristine FF environment. The problem wasn't there. After adding my custom settings to NS one by one and testing, it boiled down to this one: "Cascade top document's permissions to 3rd party scripts" under Advanced -> Trusted. Turning it on is an easy way to break NS I thought it would just work and allow me to "temporarily allow all this page" less often (yes, even automatically allowing top level sites doesn't always suffice). It would be great if there were help tooltips associated with each option when moving over it with the cursor. Thanks again, problem solved.

rihad wrote:it boiled down to this one: "Cascade top document's permissions to 3rd party scripts" under Advanced -> Trusted. Turning it on is an easy way to break NS I thought it would just work and allow me to "temporarily allow all this page" less often...Thanks again, problem solved.

Not quite solved. That option should have worked exactly as you expected, and I can't think of a way in which it would break a site that would otherwise work.

Most likely there's some strangeness in the interaction between cascading permissions and session restore, which Giorgio may be able to identify and fix. Thanks for reporting it.

Something broke further, most likely after the most recent NS auto-update. Now two distinct forum boards don't seem to have JS temporarily enabled by default at all, I have to do it manually to get them working. The "JavaScript disabled" message (the contents of <NOSCRIPT></NOSCRIPT>) doesn't appear, though. I didn't change any settings for it to break. Temporarily allow be default is still enabled. I tried choosing either one of Full addresses (default), Full domains, Based 2nd level domains and restarting, with no luck. The top sites are being correctly added to the whitelist in italics. "Cascade top doc's permissions to 3rd party scripts" is still disabled because enabling it still disables JS altogether.

rihad wrote:Now two distinct forum boards

Which? Links please?

Oops. I think it was the lack of ajax.googleapis.com among the whitelisted sites that caused the problem. Adding it there fixed it. I don't think I ever messed with the default list that came with the install. Well...