[thelist] Browser Detect with JavaScript

[Mike Smith]

I concur, although not an issue with javascript/css, I know for a fact that there are problems with versions of the Netscape browser
communicating over SSL to an NT IIS webserver that is running high encryption levels.  This is covered in a posting to newsnet,
which you can see on deja:

http://x63.deja.com/getdoc.xp?AN=591542548.1&CONTEXT=967025367.1391394840&hitnum=11

The latest version of netscape has worked around the problem.

just my 2 cents ;-)

Mike
> -----Original Message-----
> From: thelist-admin at lists.evolt.org
> [mailto:thelist-admin at lists.evolt.org]On Behalf Of Aylard JA (James)
> Sent: 01 December 2000 14:07
> To: 'thelist at lists.evolt.org'
> Subject: RE: [thelist] Browser Detect with JavaScript
>
>
> Matt,
>
> > It's my understanding that Communicator 4.08 was the latest generation 4
> > release of Navigator. All later versions of Communicator were changes in
> other
> > portions of Communicator (i.e. other than Navigator).
>
> 	This is what I have understood, too. Except I've decided that it
> can't possibly be true: Netscape has continued to patch Communicator 4.7x,
> primarily for browser holes, while leaving the stand-alone Navigator, well,
> standing alone. As well, I recall some cross-frame issues cropping up in one
> of the post-Navigator versions of Communicator. Since Netscape hasn't
> updated its 4.x documentation in three years, Navigator 4.08 and
> Communicator 4.7x are the same on paper, but in practice they are not.
>
> James Aylard
>
> ---------------------------------------
> For unsubscribe and other options, including
> the Tip Harvester and archive of TheList go to:
> http://lists.evolt.org Workers of the Web, evolt !