IE6 Ignores JavaScript's return false on a Link

[vunet.us]

Why does IE6 ignores JavaScript's return false on a link and how to
fix it? Firefox works perfect!

<a href="page1.html" onclick="return test(this)">Test</a>

JS:

function test(obj)
{
if(obj.href=='page1.html'){
doSomething();
return false;
}else{
return true;
}
}

[Randy Webb]

vu******@gmail.com said the following on 4/17/2007 12:29 PM:

Why does IE6 ignores JavaScript's return false on a link and how to
fix it? Firefox works perfect!

IE isn't ignoring the return false, it is returning true. The href
property is an absolute path in IE (test it with an alert).

<a href="page1.html" onclick="return test(this)">Test</a>

JS:

function test(obj)
{

alert(obj.href)

And you will see that the href property isn't what you expect it to be.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[vunet.us]

On Apr 17, 12:41 pm, Randy Webb <[e-mail]:

[e-mail] said the following on 4/17/2007 12:29 PM:

Why does IE6 ignores JavaScript's return false on a link and how to
fix it? Firefox works perfect!

IE isn't ignoring the return false, it is returning true. The href
property is an absolute path in IE (test it with an alert).

<a href="page1.html" onclick="return test(this)">Test</a>

JS:

function test(obj)
{

alert(obj.href)

And you will see that the href property isn't what you expect it to be.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/

Sorry, I meant this does not work:

function doSomething(){
alert('no go');
}

function test(obj)
{
if(obj.href.toString().indexOf("page1.html")!= -1){
doSomething();
return false;
}else{
return true;
}
}

[Randy Webb]

vu******@gmail.com said the following on 4/17/2007 3:18 PM:

On Apr 17, 12:41 pm, Randy Webb <[e-mail]:

>[e-mail] said the following on 4/17/2007 12:29 PM:

>>Why does IE6 ignores JavaScript's return false on a link and how to
fix it? Firefox works perfect!

IE isn't ignoring the return false, it is returning true. The href
property is an absolute path in IE (test it with an alert).

>><a href="page1.html" onclick="return test(this)">Test</a>
JS:
function test(obj)
{

alert(obj.href)

And you will see that the href property isn't what you expect it to be.

<another useless quoted signature snipped>

Sorry, I meant this does not work:

Define "does not work" as I get the alert and the URL is not followed
with a copy/paste of your code. So you must have something else
(probably in the real doSomething()) that is causing it to break.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[vunet.us]

On Apr 17, 6:00 pm, Randy Webb <[e-mail]:

[e-mail] said the following on 4/17/2007 3:18 PM:

On Apr 17, 12:41 pm, Randy Webb <[e-mail]:

[e-mail] said the following on 4/17/2007 12:29 PM:

>Why does IE6 ignores JavaScript's return false on a link and how to
fix it? Firefox works perfect!
IE isn't ignoring the return false, it is returning true. The href
property is an absolute path in IE (test it with an alert).

><a href="page1.html" onclick="return test(this)">Test</a>
JS:
function test(obj)
{
alert(obj.href)

And you will see that the href property isn't what you expect it to be.

<another useless quoted signature snipped>

Sorry, I meant this does not work:

Define "does not work" as I get the alert and the URL is not followed
with a copy/paste of your code. So you must have something else
(probably in the real doSomething()) that is causing it to break.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javascript FAQ -http://jibbering.com/faq/index.html
Javascript Best Practices -http://www.JavascriptToolbox.com/bestpractices/

I will test doSomething(), thanks. But the strange this is that it
works with FF, not IE6. I did not test IE7 or other browsers yet.

[Lee]

vu******@gmail.com said:

>Sorry, I meant this does not work:

function doSomething(){
alert('no go');
}

function test(obj)
{
if(obj.href.toString().indexOf("page1.html")!= -1){
doSomething();
return false;
}else{
return true;
}
}

Have you even considered alerting the value of obj.href before deciding that the
browser doesn't work?
--

[vunet.us]

On Apr 17, 6:13 pm, Lee <[e-mail]:

[e-mail] said:

Sorry, I meant this does not work:

function doSomething(){
alert('no go');
}

function test(obj)
{
if(obj.href.toString().indexOf("page1.html")!= -1){
doSomething();
return false;
}else{
return true;
}
}

Have you even considered alerting the value of obj.href before deciding that the
browser doesn't work?

--

I have a test case which shows that this function above works in IE6
if used apart from the whole page. Within a page, it does not work and
follows the link (when it shouldn't). I did not have a deeper look yet
but will work on that shortly. Perhaps, in a meantime, anyone may have
any suggestions for this approach: how effective it is and,
considering all other facts, what other alternative may exist.
Thanks.

[Lee]

vu******@gmail.com said:

>
On Apr 17, 6:13 pm, Lee <[e-mail]:

>[e-mail] said:

>Sorry, I meant this does not work:

>function doSomething(){
alert('no go');
}

>function test(obj)
{
if(obj.href.toString().indexOf("page1.html")!= -1){
doSomething();
return false;
}else{
return true;
}
}

Have you even considered alerting the value of obj.href before deciding that the
browser doesn't work?

--

I have a test case which shows that this function above works in IE6
if used apart from the whole page. Within a page, it does not work and
follows the link (when it shouldn't). I did not have a deeper look yet
but will work on that shortly. Perhaps, in a meantime, anyone may have
any suggestions for this approach: how effective it is and,
considering all other facts, what other alternative may exist.

The approach is fine. Either the value of obj.href is not what you
expect, or your doSomething() function contains errors.
--

[vunet.us]

On Apr 18, 9:48 am, Lee <[e-mail]:

[e-mail] said:

On Apr 17, 6:13 pm, Lee <[e-mail]:

[e-mail] said:

Sorry, I meant this does not work:

function doSomething(){
alert('no go');
}

function test(obj)
{
if(obj.href.toString().indexOf("page1.html")!= -1){
doSomething();
return false;
}else{
return true;
}
}

>Have you even considered alerting the value of obj.href before deciding that the
browser doesn't work?

--

I have a test case which shows that this function above works in IE6
if used apart from the whole page. Within a page, it does not work and
follows the link (when it shouldn't). I did not have a deeper look yet
but will work on that shortly. Perhaps, in a meantime, anyone may have
any suggestions for this approach: how effective it is and,
considering all other facts, what other alternative may exist.

The approach is fine. Either the value of obj.href is not what you
expect, or your doSomething() function contains errors.

--

Finally!

I found the problem. I have some included JS file with
document.onclick = somefunction which returned true. Hah! But how did
Firefox get away with it?.. I do not know :)

Thanks everyone!