Flasher Archive

[Previous] [Next] - [Index] [Thread Index] - [Previous in Thread] [Next in Thread]


Subject: Re: FLASH: FLASH . . . win 98 problem
From: Colin Moock
Date: Wed, 20 Jan 1999 00:10:54 GMT

flasheratshocker [dot] com,Internet writes:
>What is it that is generating
>this old code that is causing the probllem with win98 and what is that
>particular code for?
The reason the old code is a problem is that it's a pain to programmatically
grab the OS from navigator.appVersion, so you have to do it by hand like this:

if the OS is Win95
or if the browser is WinNT
or if the browser is Win98
Then do this...

Unfortunately, you can't know the names of the OSes in advance so if your
detection code relies on determining the OS, the code becomes out of date every
time appVersion reports a new OS (as in the case of Win98). It's a problem
inherent in all javascripts of this kind. This and other shortcomings of the
JavaScript detection routines for Flash make a pretty strong case for doing the
alternative kind of detection I posted a day ago which you can take a look at
here:
http://colinmoock.iceinc.com/webdesign/flash/detection/noscriptdetection.html

If you want to learn more about JavaScript browser sniffing, visit the small
section JavaScript section of my site:
http://colinmoock.iceinc.com/webdesign/javascript/index.html

colin

------------------------------------------------------------------------
To UNSUBSCRIBE send: unsubscribe flasher in the body of an
email to list-manageratshocker [dot] com. Problems to: owneratshocker [dot] com
N.B. Email address must be the same as the one you used to subscribe.
For info on digest mode send: info flasher to list-manageratshocker [dot] com


Replies
  Re: FLASH: FLASH . . . win 98 problem, Colin Moock

Replies
  FLASH: FLASH . . . win 98 problem, Daniel Votino

[Previous] [Next] - [Index] [Thread Index] - [Next in Thread] [Previous in Thread]