[WEB4LIB] More MS sabatoge of Netscape?

[Glenn Johnson-Grau]

I have just noticed this problem with Communicator 4.61, tested on several
machines. I went to the Fortres site (<http://www.fortres.com>) and noticed
that some of the links would not work in Netscape, but worked fine in IE.
At first I assumed that it was a problem with Fortres' html and was going
to write to them. What is particularly weird is that on the Fortres page,
there are two links with the identical html. It reads 

	<a href="./fortres/masterlock/index.html">Master Lock by Fortres Grand
Corporation</a> 
and

	<a href="./fortres/masterlock/index.html">-more-</a>

The link on the first one only works on the characters "ck by", meaning if
you click on "Master" or "Lo"  or "Fortres Grand Corporation" you get
nothing, but if you click on "ck by" it works. And if you click on "-more-"
it works.

I've also had pages where the links don't work, even after restarting
Communicator, unless I reboot the machine.

Are these more general problems with Communicator 4.61 or am I missing
something?

Thanks.

--Glenn

>
>Has anyone else experienced difficulty viewing Microsoft sites with
>Netscape browsers?  I have Netscape 4.61 and it keeps loosing it on the
>MSNBC web site.  Specifically, I loose the ability to click on hypertext
>links (I can click, but the new page isn't opened), and closing and
>re-opening the browser doesn't solve the problem--I have to restart the PC.
> I do have the necessary MS plugins for this site.  
>
>Also, earlier in the summer, one day I suddenly lost the ability to search
>the Microsoft support site --the pull down menus and text entry boxes just
>didn't appear on the screen.  That seems to be resolved, for now, by
>upgrading to the latest version of Netscape.
>
>Does anyone have any information about known bugs with Netscape and MS ASP
>pages?  Since Microsoft seems to be providing ever more content on the Web,
>if it is a purposely built in incompatibility, it would seem users are
>forced to use Internet Explorer to view these sites.  Of course this poses
>a problem for libraries--the choices seem to be, just use IE on public
>terminals, or constantly upgrade Netscape as these incompatibilities are
>discovered.
>
>Last, it seems disingenous to me for Microsoft to be making a case for
>"open standards" when it comes to instant messaging at the same time as
>they are constantly thwarting HTML standards.
>
>
>
>
>*-*-*-*-*-*-*-*-*-*
>Alicia Abramson
>Director, Library Information Systems
>University Library
>California State University, Sacramento
>abramson at libraryserver.lib.csus.edu
>*-*-*-*-*-*-*-*-*-*-*-*-*-*
>
>

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Glenn Johnson-Grau					    
Networked Resources/Reference Librarian			
Loyola Marymount University
Los Angeles, CA 90045-8200
(310)338-6063
gjohnson at lmumail.lmu.edu