[thelist] Netscape 6 loads page twice

[aardvark]

> From: Rob Keniger <rob at bigbang.net.au>
> 
> This is not necessarily true. Many pages coded using DHTML that required
> workarounds or hacks to work in Netscape 4.x will break in version 6. It's
> not Netscape 6's fault - it is the fault of the 4.x Netscape versions and
> their buggy CSS/DOM implementation.

i guess a case could be made for not using DHTML for that very 
reason... when you choose to use DHTML you consciously cut 
some users out... and not just the non-IE users... whether the site 
relies on those DHTML features, and by how much, determines 
how unusable the page is to other browsers...

i don't consider coding to a broken implementation to be an 
adequate excuse... but i might be the only one who thinks that...

> Fair enough, but some features of the previous browsers *require* you to use

i completely disagree with that... nothing *requires* the use of 
features... i've been building e-commerce and generic web sites for 
a while now, and i've never needed to use browser-specific features 
to make a page work... in fact, i use only supported features, with 
a smattering of unfortunate body attributes, to allow all users to 
use the page...

> features that are not part of the W3C recommendation. Ever used a name
> attribute on an image to create a rollover? Boom, your page will not
> validate. The spec calls for ID attributes on images.

um... which spec?

http://validator.w3.org/check?uri=http%3A%2F%2Froselli.org%2Fad
rian%2F

check all the pages on the site, and other than 4 pages with a 
'wrap' attribute in a textarea, the entire site validates... and all the 
images have a 'name' attribute...

it's not that hard to build pages that look decent and work for all 
users...