N
Nicolai P. Zwar
I am about to start on a quite large (and ever growing) site (with two
implemented databases), lots of pages, (maybe) a discussion forum,
Now here's the rub: the page has to function and look fairly
decent in Netscape 4x browsers, too. Haven't coded with Netscape 4x in
mind for quite a while, but there are several options I can think of
right away:
Code the entire page in a transitional tag soup, including lots of
tables, gif spacers, etc. (Urgh!) That way, it'll look more or less okay
on different browsers including Netscape 4x, but the code will be murky,
maintenance will be higher, and I'd have to provide much more commentary
as usual for possible follow up designers/coders. Anyway, that's clearly
the way I would least like to go.
Code two different pages, one for modern browsers, one for classic
browsers. (Another Urgh! Highly impractical, completely inefficient and
twice the maintenance work.)
Or, and that's the option that at this point seems to me the most
prudent option, is to code the site in strict XHTML 1.0 (or maybe even
HTML 4.01... does it make any difference in Netscape 4x?) , use a basic
set of tables for positioning, and then feed Netscape 4x a different
stylesheet based on the stuff N4 understands, and try to get it to look
halfway decent. To me, that seems to be the way to go at this point. I
usually test sites in Lynx, too, to see if the basics are there even if
all the layout's gone, so the site should be usable no matter what, but
Netscape 4x should be considered when designing the site, as quite a few
visitors will be using Netscape 4x on Unix.
Has anybody else coded with Netscape 4x in the back of his mind lately
and has anybody maybe suggestions/warnings/pieces of advice/mistakes to
avoid/other stuff that I might/could/should consider?
implemented databases), lots of pages, (maybe) a discussion forum,
Now here's the rub: the page has to function and look fairly
decent in Netscape 4x browsers, too. Haven't coded with Netscape 4x in
mind for quite a while, but there are several options I can think of
right away:
Code the entire page in a transitional tag soup, including lots of
tables, gif spacers, etc. (Urgh!) That way, it'll look more or less okay
on different browsers including Netscape 4x, but the code will be murky,
maintenance will be higher, and I'd have to provide much more commentary
as usual for possible follow up designers/coders. Anyway, that's clearly
the way I would least like to go.
Code two different pages, one for modern browsers, one for classic
browsers. (Another Urgh! Highly impractical, completely inefficient and
twice the maintenance work.)
Or, and that's the option that at this point seems to me the most
prudent option, is to code the site in strict XHTML 1.0 (or maybe even
HTML 4.01... does it make any difference in Netscape 4x?) , use a basic
set of tables for positioning, and then feed Netscape 4x a different
stylesheet based on the stuff N4 understands, and try to get it to look
halfway decent. To me, that seems to be the way to go at this point. I
usually test sites in Lynx, too, to see if the basics are there even if
all the layout's gone, so the site should be usable no matter what, but
Netscape 4x should be considered when designing the site, as quite a few
visitors will be using Netscape 4x on Unix.
Has anybody else coded with Netscape 4x in the back of his mind lately
and has anybody maybe suggestions/warnings/pieces of advice/mistakes to
avoid/other stuff that I might/could/should consider?