On Tue, 11 Mar 2003 21:37:37 +0100, Ernest E Vogelsinger wrote about "Re:
[PHP] pop-up problem" what the universal translator turned into this:
>At 21:02 11.03.2003, -{ Rene Brehmer }- said:
>--------------------[snip]--------------------
>>On Mon, 20 Jan 2003 21:48:22 +0000, Sean Burlington wrote about "Re: [PHP]
>>pop-up problem" what the universal translator turned into this:
>>
>>>I would do
>>>
>>><a href="foo.php" target="Foo" onclick="window.open('foo.php', 'Foo',
>>> 'height=480,width=640,status=yes,scrolling=no,scrollbars=no');return
>>> false;">Click Here</a>
>>>
>>>as this will still work on non-js browsers - albeit without being able
>>>to size/position the window.
>>
>>But you'd also get the same page in two windows ... one with dressing, one
>>without. Atleast in IE ... it runs both the href code, and the onclick
>>code ... when the JIT is enabled.
>>
>>On browsers where the JIT is disabled, only HREF is executed.
>--------------------[snip]--------------------
>
>No - if the onClick handler returns false, nothing will happen. That's the
>original reason for the onClick handler to be there - it can take control
>if a link is actually performed or not.
My IE doesn't care about that ... it kicks both into action ... which is
bothersome as I normally used '#' in the href when onclick was used to
open windows... so everytime you clicked the link, it'd scroll the page to
the top, while opening the new window.
The same thing happens with target (if target is _new) and # in href.
It'll load a new window, with the current page in, and try to run the
onclick function there...
Rene
--
Rene Brehmer
This message was written on 100% recycled spam.
Come see! My brand new site is now online!
http://www.metalbunny.net
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
