No more 'javascript:' commands from URL bar ?

[Pablo2]

Hello Guys,

My first ever problem with NoScript therefore my first post here.
I am running FF17.0 and tried with both NoScript 2.6.1 and 2.6.2 . Until last Thursday I was a happy user of javascript commands executed via URL bar enabled by NoScript (let it be the simplest " javascript:alert('abc') " ). But yesterday to my despair I found out I could get nothing executed that way. I tweaked with noscript.allowURLBarJS value, I reinstalled NoScript few times. Nothing has changed though.
I am sure that those of you guys who read this forum have much broader knowledge - could anyone suggest me what can I do to get my favorite feature back ?

[therube]

Confirmed.

All that I see?:

Code: Select all

Sat Nov 24 2012 12:25:30
Error: TypeError: this.mCurrentBrowser is undefined
Source file: chrome://browser/content/tabbrowser.xml
Line: 2316

Code: Select all

            return this.mCurrentBrowser.loadURIWithFlags(aURI, aFlags, aReferrerURI, aCharset, aPostData);

SeaMonkey is unaffected.


But there's more to it then just that.
Haven't figured it out yet ...
(perhaps only occurs on start up, first window ...?)


Heh, I know what it is, let me find it ...

[therube]

javascript:alert("Hello World!")

javascript: / data: URI being bypassed

or was it the about:newtab bug?

Perhaps neither, or a combination of both, but javascript: is not firing from about:newtab.


(SeaMonkey has no about:newtab.)

[Pablo]

therube, thanks for looking into the issue. I've looked at the forum today again and this is because of the ABP enabled, same issue is described here http://forums.informaction.com/viewtopi ... 10&t=11080

[therube]

Actually I think not.

Believe it is a combination of two things.

One, it is not working in about:newtab.

Two:

The site that you open in the tab should not have NoScript "permissions" assigned to it.
So open some random site that is not allow, like http://www.example.com/.

If you do yahoo or msn or something on your whitelist, you will not see the bug.

(So if you had Allow Scripts Globally enabled, it would not work at all.)

[therube]

And I think there is even more going on then that.

I'm now thinking that Allow Scripts Globally is an issue unto itself.
about:newtab is an issue unto itself.

Otherwise, a particular domain being allowed or not, may not be an issue, not sure, because now, at times, other then the two mentioned above, it all seems to be working? So there has to be more yet.

Not seeing how ABP relates at all?

[Pablo]

In case there was either a blank tab or 'Allow Scripts Globally' option enabled I have never been able to run javascript from url. But only on Friday (Nov 23th) javascript from url stopped working completely. Disabling ABP 'fixed' that.
Personally I don't care for not being able to run javascript on a blank tab, but it would be great if it was possible with 'Allow Scripts Globally' enabled.

[Giorgio Maone]

Work-around in latest development build 2.6.3rc1.