RE: Feed Back on compatibility

Folow up about the tidbit, i found it on the web, oh, bet it must be at
least a couple of years old.

I do not use a lot of javascript, but I do remember that if you choose to
account for various browser versions, Netscape 2.xx gets a bit tricky.

For example, ver 2.02 will display code BOTH within the hidden script AND
within the <noscript> tag. If memory serves, other NS versions would ignore
the hidden javascript and only display the <noscript> contents.

Naturally you will get differing results if using javascript 1.0 vs 1.1,
jscript, etc..

If any gurus have a correction to my post, it will be graciously and
thankfully received.

Peter

>
> ***************  tidbit found on my puter
> Don't forget Navigator 2.x
> If your site has to support both JavaScript-capable and
> non-JavaScript-capable browsers, you may have tried to use the
> <SCRIPT> and
> <NOSCRIPT> tags to create separate content for the non-JavaScript
> browsers.
> And you may have noticed that Navigator 2.x does not support the
> <NOSCRIPT>
> tag--even though it is JavaScript-capable, it displays the <NOSCRIPT>
> content anyway.
>
> In order to mask the text-only <NOSCRIPT> content from Navigator 2.x, you
> must place the text-only content and the JavaScript-enhanced content in
> separate files and selectively direct browsers from your main page to the
> appropriate text-only or JavaScript page via a pair of separately targeted
> links:
>
> <A href="nonJSPage.html" onclick="location='JSPage.html';return
> false">Go to
> Info Page</A>
>
> JavaScript browsers evaluate the onClick event handler first, and thus get
> sent to the JavaScript version of the page. Since the return is false,
> JavaScript-capable browsers won't go on to the page listed in the anchor.
> Non-JavaScript browsers ignore the JavaScript event handler entirely and
> follow the normal HTML link to the non-JavaScript page.
> *********************** end of tidbit

HTML: hwg-critique mailing list archives, maintained by Webmaster @ IWA