Re: netscape window control failing

You are correct.

The JavaScript Protocol Specifies that the URL is JavaScript code.
With Event handlers its assumed that javascript is the default scripting
language.

I have not found any documentation on using or not using the javascript:
protocol with an event handler as of yet. I have however witnessed failures
of event handlers  that were corrected using the javascript: protocol.

Rythmist

Examples:

<A HREF="javascript:alert('JavaScript Link!');">JavaScript Link</A>
<A HREF="javascript:window.open('about:blank','New',''">Open Window</A>
<A HREF="javascript:window.close()">Close Window</A>
<A HREF="javascript:history.back()">Previous Page</A>



----- Original Message -----
From: "Cyanide _7" <leo7278(at)hotmail.com>
To: <Rythmist(at)gamewood.net>
Cc: <hwg-languages(at)hwg.org>
Sent: Tuesday, August 22, 2000 9:40 PM
Subject: Re: netscape window control failing


> what? "javascript:" i thought was merely the protocol to specify that the
> following code is javascript code as opposed to a URL. mailto is another
> example. protocols that end in // usually are followed by a url, and the
> protocol merely defines how the resource should be servered. you should
not
> use a protocol in an event handler, as they are automatically assumed to
be
> the default client-side scripting language. if this is wrong, could you
> please correct me and point me in the direction of the porper
documentation?
> TIA - Cyanide_7
>
> >
> >Also your links with onClick should include javascript:.
> >Example: onClick="javascript:history.back()"
> >

HWG: hwg-languages mailing list archives, maintained by Webmasters @ IWA