Re: when using validator is not sensible

In my experience, the source of most problems with interoperability is
Netscape 4.* (I'm not talking about earlier versions of Netscape, they're
simply obsolete) It seems to have a whole different idea of HTML and CSS. It
ignores some attributes, others result in weird and totally unpredictable
results, while IE and Opera in most cases properly display a site with valid
HTML and CSS. There were *many* obvious cases where valid and seeemingly
normal HTML caused NN to crash, display a blank page or smth like that. With
CSS it's much worse. Its incomplete and buggy implementation of CSS is very
annoying.
In implementing my last website's design, we had to resort to multiple-level
nested tables with a fine mix of CSS and non-CSS attributes, because that's
the *only* way NN would properly display all borders and colours.
I wish I could make a valid [X]HTML/CSS page and count on it being displayed
properly in every browser, but... numerous workarounds are required for
those blasted non-conforming browsers. They're slowing down the progress and
making my life miserable. I'm tired of this.
Any advice on this problem will be greatly appreciated.
-------------
Or sould we just ignore older NN in the hopes that it will gradually go
away? But then, many users (although not the majority) still use it just
because they're used to it..

Received on Thursday, 16 August 2001 12:49:38 UTC