Previous Message
Next Message

Re: [css-d] Divergence between compliant browsers

Sent by aardvark on 30 January 2002 00:12

> From: Ben Henick [EMAIL-REMOVED]>
> > I hate to be pedantic here (well, actually I love being
> > pedantic ;)) but CSS doesn't help you seperate content from
> > structure.. a cms will do that for you. or using xml, since
> Erm, actually it does.  If you say, "put the scripting here, the
> presentation here, and the content here," voila!  All that's left is
> the markup, which in many ways is tied to the logic anyway (thus the
> CMS).

well, i'm with the previous post...

CSS can help you split your *style* from your *structure*... that's 
it... your content should then be independent of your structure...

so a good CMS can output to the structure of HTML2, WML, 
XHTML, whatever... then you style it with CSS, or in the case of 
HTML 2 (for example), right in the structure...

i've never understood the argument that using CSS splits your style 
from your content... the content has nothing to do with it, it splits 
style and structure...

to go back to those three points ben mentioned earlier (that the 
move to CSS and standards is about three things):
> 1.  Ease of maintenance
> 2.  Separation of style/content/structure
> 3.  Forward compatibility

ease of maintenance should be moot in a good shop that uses 
templates and the like... yes, updating an entire site in one CSS 
file rocks, but i do the same thing in one HTML template as well... 
so this boon in maintenance everyone talks about is old hat to me...

the second one is somewhat inaccurate... style and structure i'll 
buy, but not content... if your content is embedded in all your 
individual pages of code, wrapped in divs and all, then you've failed 
to separate your structure and content... back to the drawing board 
with you, because when you need to update the site and move 
things out of one div into another, you're screwed...

forward compatibility is also a flawed argument... look at all the 
hacks on this list today... killing scrollbars because the designer 
doesn't like them?  what about the next generation of browsers, 
how will they like that?  using empty script blocks to address the 
unstyled flash in IE?  c'mon, people, that's all hacking, and all 
should damn well break later, better browsers...

no, backward-compatibility overrides forward compatibility for my 
clients most of the time, and backward-compatibility is a stationary 
target... and that usually doesn't require hacks...

CSS is all too often an add-on for pages that otherwise work well... 
yes, that sucks, and i don't like it, but CSS positioning support is 
still small compared to my audiences...
Previous Message
Next Message

Message thread:

Possibly related: