Re: Frames and JS

["Brian Karlak" <bkarlak@panbio.com>]

On Feb 27,  5:55pm, Chris Moses wrote:
> Subject: Frames and JS

> 1. Do not use a <a href=... onclick="newurl()"> format. The problem is
> that this causes Navigator to try to go to the url specified in the JS and
> the url specified in the anchor. Result=blowup

Actually, you can use a slight modification of this format.  I use <a href=...
onclick="newurl()" target=FRAME1> where FRAME1 gets the URL specified in the
href portion and newurl() is programed to dump it's info into FRAME2.

I like this method because it lets me keep the standard link format.  Buttons
can be messy and large at times.  What's extra nice about this method is that
the href link can be essentially a dummy by pointing it to a frame that is
either very small or has static information in it, and you now have hyperlinked
text that runs a JavaScript function!

Brian

-- 
  d a t a b a s e s    a r e   i n   o u r  g e n e s
  ----------------------------------------------------
  Brian Karlak   bkarlak@panbio.com  (510) 337-7910 ph
  Manager, SciApps Group             (510) 522-9394 fx
  ----------------------------------------------------
  P  A  N  G  E  A     S  Y  S  T  E  M  S     I  N  C
--------------------------------------------------------------------
This message came from the mailing list javascript. For help using the
mailing list software, please send a message to 'majordomo@obscure.org'
with the message body 'help'. To unsubscribe, send a message to
'majordomo@obscure.org' with the message body 'unsubscribe javascript'.