W3C home > Mailing lists > Public > www-style@w3.org > December 2004

Re: What is missing in CSS?

From: Brian Sexton <discussion-w3c@ididnotoptin.com>
Date: Mon, 6 Dec 2004 06:56:12 -0800
Message-ID: <001401c4dba3$bac21410$651aa143@desktop>
To: <Slalomsk8er@solnet.ch>
Cc: <www-style@w3.org>

Dominik et al,

> Look at the example code, this is a realy old concept in programming
> (if (x > 0) => do foo; else => do bar).
> But it makes no sense with out constants and variables.

Unfortunately, it is the programmatic nature that will likely doom it.

>> If it's introduced, you will need to "hack" for every existing
>> browser, since none will support it.
> Yes, They will be the older Browsers then.
> Some clever masking for new and old browsers would be good, I realy
> start to hate all the browser hacks.
> Do the browsers ignor statements they do not understand, if so the
> masking is just needed for new browsers to hide the old browser code?

In theory, user agents ignore CSS they do not understand, but the 
implementation is not consistent, thus enabling CSS hacks.  If we had 
something as simple as version-numbered blocks of CSS, this would not be a 
problem because user agents could just assume that they do not understand a 
block with a version number above their highest-implemented support--not 
just new properties, but new syntax as well as long as it fell within 
designated block delimiters--and they could still attempt to parse 
higher-numbered blocks if desired (preferably with a disclaimer for the user 
about the results possibly not being ideal) while developers could support 
multiple versions of CSS simultaneously, but since we do have any of that 
(unless you count import commands or alternate style sheets), we need to use 
other methods to ensure the best results with maximum compatibility.

Kind regards,

Brian Sexton 
Received on Monday, 6 December 2004 14:56:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:16 UTC