Pop up with strange behaviour in Internet Explorer but not Firefox.

[ft310]

Use Internet Explorer go to http://rhodeisland-aa.org/tester/meetings/index.htm

On the left click "and go to meetings"

Click any address in the right hand 'location' column.

The entire page reloads in the frame. (Bad)

Perform the same test using Firefox

The entire page does not reload. (Good)

In both cases the disclaimer window appears and the application
continues. That is good, but the IE behaviour is not good.

I know I am doing something wrong -- please tell me.

Thank you.

[noagbodjivictor]

I'm using FF2 and the entire page does reload too.

[noagbodjivictor]

Pay no attention to what I wrote earlier. You are right.

[noagbodjivictor]

Ok. This is what you have to do. Put something in the href="";
otherwhise, IE will fill it for you to http://rhodeisland-aa.org/tester/meetings/,
which will cause the entire page to reload.

But. It seems like FF is replacing it with the current URL in the
address bar.

Put something like href="#".

[Lee]

no************* @gmail.com said:

>
Ok. This is what you have to do. Put something in the href="";
otherwhise, IE will fill it for you to
http://rhodeisland-aa.org/tester/meetings/,
which will cause the entire page to reload.

But. It seems like FF is replacing it with the current URL in the
address bar.

Put something like href="#".

More important is that the onclick handler return false, so the
browser doesn't try to follow the link.

<a href="#NoLuckIf ScriptDisabled"
onclick="launch (610);return false">Sturdy Hospital Auditorium, 211 Park Street
02703</a>
--

[ft310]

On May 29, 9:57 pm, Lee <REM0VElbspamt. [e-mail] :

noagbodjivic... @gmail.com said:

Ok. This is what you have to do. Put something in the href="";
otherwhise, IE will fill it for you to
http://rhodeisland-aa.org/tester/meetings/,
which will cause the entire page to reload.

But. It seems like FF is replacing it with the current URL in the
address bar.

Put something like href="#".

More important is that the onclick handler return false, so the
browser doesn't try to follow the link.

<a href="#NoLuckIf ScriptDisabled"
onclick="launch (610);return false">Sturdy Hospital Auditorium, 211 Park Street
02703</a>

--

Thank you - this is great.

Are you using some debugger to get this or is it just a superior
development of your craft?
Thanks

Frank Toohey

[Randy Webb]

ft310 said the following on 5/29/2007 11:15 PM:

On May 29, 9:57 pm, Lee <REM0VElbspamt. [e-mail] :

>noagbodjivic.. [e-mail] said:

>>Ok. This is what you have to do. Put something in the href="";
otherwhise, IE will fill it for you to
http://rhodeisland-aa.org/tester/meetings/,
which will cause the entire page to reload.
But. It seems like FF is replacing it with the current URL in the
address bar.
Put something like href="#".

More important is that the onclick handler return false, so the
browser doesn't try to follow the link.

<a href="#NoLuckIf ScriptDisabled"
onclick="launc h(610);return false">Sturdy Hospital Auditorium, 211 Park Street
02703</a>

--

Thank you - this is great.

Are you using some debugger to get this or is it just a superior
development of your craft?

It is a superior development of the craft with some sorcery thrown in
for fun. It can be learned from the group FAQ and the archives though.
Personally, I don't care for the onclick="launch (160);return false", I
prefer onclick="return launch(160)" and let the launch function return
true or false. You can search the archives to find out why return
functionName is a better alternative.

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

[ft310]

On May 30, 12:27 am, Randy Webb <HikksNotAtH... @aol.comwrote:

ft310 said the following on 5/29/2007 11:15 PM:

On May 29, 9:57 pm, Lee <REM0VElbspamt. [e-mail] :

noagbodjivic... @gmail.com said:

>Ok. This is what you have to do. Put something in the href="";
otherwhise, IE will fill it for you to
http://rhodeisland-aa.org/tester/meetings/,
which will cause the entire page to reload.
But. It seems like FF is replacing it with the current URL in the
address bar.
Put something like href="#".
More important is that the onclick handler return false, so the
browser doesn't try to follow the link.

<a href="#NoLuckIf ScriptDisabled"
onclick="launch (610);return false">Sturdy Hospital Auditorium, 211 Park Street
02703</a>

--

Thank you - this is great.

Are you using some debugger to get this or is it just a superior
development of your craft?

It is a superior development of the craft with some sorcery thrown in
for fun. It can be learned from the group FAQ and the archives though.
Personally, I don't care for the onclick="launch (160);return false", I
prefer onclick="return launch(160)" and let the launch function return
true or false. You can search the archives to find out why return
functionName is a better alternative.

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

Randy Again thanks -- love your answer -- it you got it . . .

The hint about the return will be implemented immediately.

[-Lost]

Randy Webb wrote:

>Are you using some debugger to get this or is it just a superior
development of your craft?

It is a superior development of the craft with some sorcery thrown in
for fun. It can be learned from the group FAQ and the archives though.
Personally, I don't care for the onclick="launch (160);return false", I
prefer onclick="return launch(160)" and let the launch function return
true or false. You can search the archives to find out why return
functionName is a better alternative.

Could you perhaps provide a search string to that effect?

I tried "return functionName" just in case, and well, it was not
satisfactory to say the least.

I am quite happy to know that I already subscribed to this method of
coding though. Why it is necessarily better I do not know. I did it
because it just made sense to reduce clutter in your markup and two,
because, why not have the function do it for you?

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.

[Randy Webb]

-Lost said the following on 5/30/2007 11:23 AM:

Randy Webb wrote:

>>Are you using some debugger to get this or is it just a superior
development of your craft?

It is a superior development of the craft with some sorcery thrown in
for fun. It can be learned from the group FAQ and the archives though.
Personally, I don't care for the onclick="launch (160);return false", I
prefer onclick="return launch(160)" and let the launch function return
true or false. You can search the archives to find out why return
functionName is a better alternative.

Could you perhaps provide a search string to that effect?

I could probably come up with one if I searched and looked long enough.
It is quicker and easier to explain it though.

I tried "return functionName" just in case, and well, it was not
satisfactory to say the least.

I am quite happy to know that I already subscribed to this method of
coding though. Why it is necessarily better I do not know.

Then why do you use a method that you don't know why it is better? :)

I did it because it just made sense to reduce clutter in your markup and two,
because, why not have the function do it for you?

In this code:

onclick="someFu nction();return false"

If someFunction has a coding error in it where it causes an error, then
the return false never gets executed and the browser will navigate to
the href property of the A element. With this code:

onclick="return someFunction()"

If someFunction has an error in it then it essentially returns false (I
believe it actually ends up as return null which type converts to return
false) and cancels the navigation.

Makes debugging a lot easier when the browser isn't navigating away on you.
--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/