469,646 Members | 1,136 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,646 developers. It's quick & easy.

Firefox Javascript Console opens with no errors on opening window

This is a framed webpage with the navigation bar in "NavBar" and the main
window in "Main".

When opening a new page in "Main" from "NavBar" with:

function OpenFrameWindow(src)
{
var NewWindow = window.open(src, "Main");
NewWindow.focus();
}

or when opening a page in a new window with:

function OpenNewWindow(src, vName, vWidth, vHeight, vLeft, vTop, vResize,
vToolbar, vScroll, vMenu)
{
var NewWindow = window.open(src, vName, "width=" + vWidth + ",height=" +
vHeight + ",left=" + vLeft + ",top=" +vTop+ ",resizable=" + vResize +
",toolbar=" + vToolbar + ",scrollbars=" + vScroll + ",menubar=" + vMenu);
NewWindow.focus();
}

the Firefox Javascript Console window opens showing no errors (All is
clicked).

Any help with this greatly appreciated.


Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com
Dec 27 '05 #1
5 1962
Roger Withnell wrote:
This is a framed webpage with the navigation bar in "NavBar" and the main
window in "Main".
OK.
When opening a new page in "Main" from "NavBar" with:

function OpenFrameWindow(src)
{
var NewWindow = window.open(src, "Main");
NewWindow.focus();
}

or when opening a page in a new window with:

function OpenNewWindow(src, vName, vWidth, vHeight, vLeft, vTop, vResize,
vToolbar, vScroll, vMenu)
{
var NewWindow = window.open(src, vName, "width=" + vWidth + ",height=" +
vHeight + ",left=" + vLeft + ",top=" +vTop+ ",resizable=" + vResize +
",toolbar=" + vToolbar + ",scrollbars=" + vScroll + ",menubar=" + vMenu);
NewWindow.focus();
}

the Firefox Javascript Console window opens showing no errors (All is
clicked).


Why would you expect error messages, provided either of both methods are
called correctly?
PointedEars
Dec 27 '05 #2
Thomas 'PointedEars' Lahn said the following on 12/27/2005 1:05 PM:
Roger Withnell wrote:

<snip>
the Firefox Javascript Console window opens showing no errors (All is
clicked).

Why would you expect error messages, provided either of both methods are
called correctly?


I think he is saying that it opens on its own. Which would be an error
in Firefox itself.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Dec 27 '05 #3
Randy Webb wrote:
Thomas 'PointedEars' Lahn said the following on 12/27/2005 1:05 PM:
Roger Withnell wrote: <snip>
the Firefox Javascript Console window opens showing no errors
(All is clicked).

Why would you expect error messages, provided either of both
methods are called correctly?


I think he is saying that it opens on its own. Which would be an
error in Firefox itself.


You may recall that typing 'javascript:' into the location bar on a
Gecko browser opens the javascript console. I was wondering whether - <a
href="javascript:" onclick="something();"> ... </a> - would do the same.
It might be expected to, but I cannot be bothered to test that right
now. If it does then it would not really be an error, and the OP's issue
becomes a failure to cancel the default action of the click event.

Richard.
Dec 28 '05 #4
Richard Cornford said the following on 12/27/2005 7:16 PM:
Randy Webb wrote:
Thomas 'PointedEars' Lahn said the following on 12/27/2005 1:05 PM:
Roger Withnell wrote:
<snip>
the Firefox Javascript Console window opens showing no errors
(All is clicked).

Why would you expect error messages, provided either of both
methods are called correctly?


I think he is saying that it opens on its own. Which would be an
error in Firefox itself.

You may recall that typing 'javascript:' into the location bar on a
Gecko browser opens the javascript console. I was wondering whether - <a
href="javascript:" onclick="something();"> ... </a> - would do the same.
It might be expected to, but I cannot be bothered to test that right
now. If it does then it would not really be an error, and the OP's issue
becomes a failure to cancel the default action of the click event.


It does exactly what you thought it would. It opens the console with no
error messages.

I guess it can be added to the pitfalls of javascript: URI's :)

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Dec 28 '05 #5
Richard Cornford wrote:
Randy Webb wrote:
Thomas 'PointedEars' Lahn said the following on 12/27/2005 1:05 PM:
Roger Withnell wrote:
the Firefox Javascript Console window opens showing no errors
(All is clicked).
Why would you expect error messages, provided either of both
methods are called correctly? I think he is saying that it opens on its own. Which would be an
error in Firefox itself.


You may recall that typing 'javascript:' into the location bar on a
Gecko browser opens the javascript console.


Not only Gecko-based ones. It happens in all Mozillas I know
(incl. Mozilla/x.y, 2 < x < 5, i.e. Netscape < 6).
I was wondering whether - <a
href="javascript:" onclick="something();"> ... </a> - would do the same.
It does. I did not think of that.
It might be expected to, [...]


It is. `javascript:' (_as-is_) indeed is an URI (RFC3986), technically
speaking.
PointedEars
Dec 28 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.

By using this site, you agree to our Privacy Policy and Terms of Use.