Why do I need to enable a domain each time I return to a tab

[nerotic]

Just noticed this new "feature" this morning, that NoScript is no longer saving that I allow pages.

Even without closing the browser if I simply change tabs and come back I see the red blocked indicator in my status bar.

What changed? And how can I fix it?

[Giorgio Maone]

There's no "new feature" like that.
What did you install recently?

[nerotic]

Hi Giorgio,

I haven't installed anything new in terms of extensions, they're the same ones I've had for weeks now.

Something else that is new is that URLs are now wrapped in brackets. You can see it in the screenshot



I hadn't seen NoScript behaving this way until today.

Any ideas?



Even with this forum, as soon as I went to upload the screenshot, as soon as I came back to the tab noscript shows informaction.com as blocked.

[Giorgio Maone]

Please check whether you inadvertently set the NoScript Options|Behavior|Forbid active web content unless it comes from a secure (HTTPS) connection option to anything but "Never".

[nerotic]

Please check whether you inadvertently set the NoScript Options|Behavior|Forbid active web content unless it comes from a secure (HTTPS) connection option to anything but "Never".

It's set to never...what else could it be?

[Scott_L]

I'm in the same boat. This all started a few days ago on each computer I use. My behavior under HTTPS is also set to "Never". I see the square brackets [ ] around the URL in NoScript on some pages but not others. I haven't added any Add-ons or Plug-ins, only done updates - and I think NS and "Load Tabs Progressively" are the only ones that have updated recently. What's odd is that the pages I hit constantly and have allowed are in the NoScript Whitelist.

Looking forward to the fix to this issue! Thanks.

[Giorgio Maone]

This means that another extension (not NoScript, if you've got the option set to "Never") is disabling Java at the tab (docShell) level.
Please try Standard Diagnostic to find the offending extension.

[Scott_L]

... I haven't added any Add-ons or Plug-ins, only done updates - and I think NS and "Load Tabs Progressively" are the only ones that have updated recently. ...

And there's the answer! nerotic, are you using Load Tabs Progressively? I disabled it, restarted FF and NoScript it's working as it always did. I'm going to go back to the previous version of LTP for now until one side or the other fixes the issue. I'll point my finger at the new guy (Load Tabs P'ly) for now.

Thanks for a great safe surfing solution Giorgio. Hey, someone should trademark that

[ithinc]

This means that another extension (not NoScript, if you've got the option set to "Never") is disabling Java at the tab (docShell) level.
Please try Standard Diagnostic to find the offending extension.

Hello, I'm the author of LTP. LTP is not disabling Java or something similar. LTP has wrapped the access to browser.webNavigation though. Please check how NoScript works.

[Morbus]

I have this problem too after installing BarTab. This will happen on tabs (sites?) that I choose in the whitelist (of BarTab) to never unload. ONLY on those. Tabs that unload automatically work perfectly fine.

This doesn't really bother me, but I'm thinking that since AppTabs in Firefox 4 will have BarTab-like functionality, NoScript will want to fix this bug...

[Giorgio Maone]

Hello, I'm the author of LTP. LTP is not disabling Java or something similar. LTP has wrapped the access to browser.webNavigation though. Please check how NoScript works.

Hello, your browser.webNavigation wrapping is broken.
The "original" browser.webNavigation implements nsIDocShell. Your wrapping doesn't, and this is the bug of yours causing NoScript to malfunction.
Try the following in Error Console with and without Load Tabs Progressively to see what I mean:

Code: Select all

alert(top.opener.gBrowser.selectedBrowser.webNavigation instanceof Components.interfaces.nsIDocShell)

I have this problem too after installing BarTab. This will happen on tabs (sites?) that I choose in the whitelist (of BarTab) to never unload. ONLY on those. Tabs that unload automatically work perfectly fine.

I installed BarTab but couldn't reproduce. Could you provide me with step-by-step instruction to reproduce this issue on a clean profile with just NoScript & BarTab installed?
Thanks.

[Morbus]

Sorry about that but I can't. I have other stuff to worry about right now Creating a new profile, installing stuff, doing what I did, and then maybe it's BarTab WITH another of my 100+ extensions that's causing the issue... Ah, the world of hurt of troubleshooting. Now way mate! If it's just me, I can live with it.

[NotAtHome]

SAME BUG ! YES, i am not alone in the world !

Strange bug with NoScript 1.9.9.90 and Firefox 3.6.4 Build 7

Thanks to help me.

[ithinc]

Hello, your browser.webNavigation wrapping is broken.
The "original" browser.webNavigation implements nsIDocShell. Your wrapping doesn't, and this is the bug of yours causing NoScript to malfunction.
Try the following in Error Console with and without Load Tabs Progressively to see what I mean:

Code: Select all

alert(top.opener.gBrowser.selectedBrowser.webNavigation instanceof Components.interfaces.nsIDocShell)

I don't know exactly how instanceof operator works, but if you try the following code, you'll find the nsIDocShell is indeed implemented.

Code: Select all

alert(top.opener.gBrowser.selectedBrowser.webNavigation.QueryInterface(Components.interfaces.nsIDocShell))

[Giorgio Maone]

Hello, your browser.webNavigation wrapping is broken.
The "original" browser.webNavigation implements nsIDocShell. Your wrapping doesn't, and this is the bug of yours causing NoScript to malfunction.
Try the following in Error Console with and without Load Tabs Progressively to see what I mean:

Code: Select all

alert(top.opener.gBrowser.selectedBrowser.webNavigation instanceof Components.interfaces.nsIDocShell)

I don't know exactly how instanceof operator works, but if you try the following code, you'll find the nsIDocShell is indeed implemented.

Code: Select all

alert(top.opener.gBrowser.selectedBrowser.webNavigation.QueryInterface(Components.interfaces.nsIDocShell))

The instanceof operator calls QueryInterface internally, and it's actually the preferred way to cast interfaces in JavaScript .
Load Tabs Progressively completely screws up this because, as far as I can see, you tried to be "smart" and didn't implement QueryInterface() at all (nor any other method of webNavigation, for the matter), but used the __noSuchMethod__() catch-all trick, which is not "seen" by XPConnect at interface resolution time and therefore breaks instanceof (and possibly other XPCOM-related machinery). Technically speaking you're not implementing any interface, even though some code may see them as implemented.

So you've got a serious bug there, which may have more unintended consequences than just breaking NoScript.
I strongly advice you to fix it by implementing your webNavigation wrapper in a less lazy fashion, even though NoScript tries to work-around your bug in latest development build.
On a side note, webNavigation gets cast to most of its interface early, so to avoid unnecessary QueryInterface() calls throughout the browser front-end code. Therefore I also advice you to query those interfaces as soon as you create your wrapper, so that code which expects webNavigation to be already cast doesn't break either.