Page 1 of 1

Problems with javascript in the address bar

Posted: Sat May 28, 2011 1:39 pm
by obiwan
With NoScript enabled, javascript entered into the address bar on a blank tab doesn't work, even with noscript.allowURLBarJS set to true.

Steps to reproduce:

1) Open a new blank tab
2) Type

Code: Select all

javascript:alert ("hello")
in the address bar and press Enter.

Results:

With NoScript disabled, an alert box is displayed.
With NoScript enabled, nothing happens.
With NoScript enabled but Allow Scripts Globally set, an alert box is displayed.

Any ideas? I've checked that about:blank is allowed, if that makes any difference.

Re: Problems with javascript in the address bar

Posted: Sat May 28, 2011 1:49 pm
by Giorgio Maone
That's due to some weird Mozilla internal implementation details.
It's worked around in latest development builds.

Re: Problems with javascript in the address bar

Posted: Sat May 28, 2011 1:57 pm
by obiwan
OK, thanks.

Re: Problems with javascript in the address bar

Posted: Tue Jul 05, 2011 6:00 am
by lisa
additional person with similar problem. Noscript is blocking my javascript in the address bar, but I do not know how to change the noscript.allowURLBarJS setting to true. maybe this is an easy fix if you can explain it to me (as simple as possible please), i've looked all through the NoScript <options> file and can't find that particular bar.

Re: Problems with javascript in the address bar

Posted: Tue Jul 05, 2011 8:43 am
by Giorgio Maone
lisa wrote:additional person with similar problem. Noscript is blocking my javascript in the address bar, but I do not know how to change the noscript.allowURLBarJS setting to true. maybe this is an easy fix if you can explain it to me (as simple as possible please), i've looked all through the NoScript <options> file and can't find that particular bar.
Open about:config, locate the relevant line and double click it.
Please notice, though, that next Firefox version will prevent address bar JavaScript from interacting with the current page, making it mostly useless anyway.

Re: Problems with javascript in the address bar

Posted: Tue Jul 05, 2011 2:59 pm
by therube
I'm still on 2.1.2rc1 so don't know if it holds true in 2.1.2rc3, but ...

Code: Select all

javascript:alert ("hello")
... brings up the NoScript warning.

Though if you load about:config (even without "entering" [accepting the prompt], much less modifying the associated Preference), then the warning is bypassed for subsequent actions in that window.

Re: Problems with javascript in the address bar

Posted: Tue Jul 05, 2011 7:58 pm
by therube
Though if you load about:config (even without "entering" [accepting the prompt], much less modifying the associated Preference), then the warning is bypassed for subsequent actions in that window.
Ditto with 2.1.2rc3.

Re: Problems with javascript in the address bar

Posted: Tue Jul 05, 2011 10:36 pm
by therube
Maybe this is a SeaMonkey specific issue?

(Not sure if NoScript is "on" in FF5 or not? I installed it, but only the "message at the bottom" shows, no icon or anything like that even though I do have the Add-on bar displaying. Or do I need to customize & drag ...? I sure don't understand this FF critter. So that's normal now, in FF, that no [NoScript|FlashGot] icons display unless you manually customize?)

Re: What makes SeaMonkey different?

Posted: Thu Aug 04, 2011 4:38 am
by therube
therube wrote:
Maybe this is a SeaMonkey specific issue?
Bump for thoughts?

Re: Problems with javascript in the address bar

Posted: Fri Oct 14, 2011 12:09 pm
by cael
it seems that the new firefox 7.0.1 has no noscript.allowURLBarJS
sorry im a noob about this thing i just really need to know how to enable it :?

Re: Problems with javascript in the address bar

Posted: Fri Oct 14, 2011 2:44 pm
by therube
> seems that the new firefox 7.0.1 has no noscript.allowURLBarJS

Correct.

Install NoScript, & as it is a NoScript preference, it will then show up.

Re: Problems with javascript in the address bar

Posted: Tue Nov 22, 2011 7:49 pm
by therube
Just a quick note that this oddity still exists in SeaMonkey 2.7a2.
Mozilla/5.0 (Windows NT 5.1; rv:10.0a2) Gecko/20111119 Firefox/10.0a2 SeaMonkey/2.7a2