That wouldn't be a failing of CSS, but rather, of the older, very outdated (as opposed to IE6, which is just outdated) browsers. To expect someone to upgrade their browser I think is much more reasonable than to expect them to support Flash, or some other plug-in. I'm not commenting on whether or not it's reasonable, just more versus less.Gotta wrap it in <p></p> and center the contents of the paragraph?
I wouldn't say mutually exclusive, but rather, the more you support one, the less you generally have of the other.This also raises a more general newbie question, but nice and philosophical: are the goals of writing markup and css for old browsers and future browsers mutually exclusive?
Always best to learn it right first, an then learn the hacks.I want to learn to write "good" markup and css --
Depends on to what extent you support the older browsers. If your Web site is for the NS4 Users Group, then, by all means, use tables for layout. Otherwise, your markup should have no bloat, or at worst, a few extra div's. As far as CSS goes, it's not so simple. IMHO, part of what "coding to standards" means is an avoidance of pixel perfect layouts and designs. As a rule of thumb, I would say a site should be 100% functional across the board, basic design geared towards IE6 (and maybe IE5+), bells and whistles for the modern browsers (Mozilla, Opera, and where reasonable, IE6)If you attempt to accommodate older browsers, does your good clean robust and standard markup and css start to fall apart?
Mordechai
***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
