Luke has posted a very thoughtful article inspired by my Myth of CSS post. (Thank you Feedster for making ego searches so easy.)
Many of the initial comments and related posts I got were focused on semantic tag meaning and if I was equating DIVs with TABLEs (obviously I’m not). Luke puts forth some cool ideas, particularly the proposed future stylesheet.
He also talks about the value of grouping elements together in a page based on their relationship to each other. I agree there is definitely some value in this and taken one step further we can see how we might use groupings to limit the scope of XFN attributes for reasons Geof pointed out recently.
One question I don’t tackle in my post is:
Should there be 100% separation of presentation and content using XHTML and CSS?
I don’t necessarily think there should, though I’m willing to be convinced otherwise. XHTML is still a presentation language; it’s designed to be displayed by a browser, not processed by an XML parser. Is there benefit from using CSS to keep the styling all in one place? Absolutely. Does it mean we need to strip all presentation related code from the XHTML? I don’t know, but I don’t think it does.
Interesting discussion and ideas; blogs are cool. 😎
Well, I think XHTML is about presentation, but only in the sense that it’s about marking up content for presentation. I consider XHTML to be structure and CSS to be window dressing.
Hmm – in that context, the :scare: extra :/scare: DIV and SPAN tags aren’t really extra, are they?
They’d be like crown molding, really — nice to have, I guess, but looks like crap until you paint it.