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

Re: Proposal: version at-rule

From: David Woolley <david@djwhome.demon.co.uk>
Date: Tue, 16 Mar 2004 21:20:47 +0000 (GMT)
Message-Id: <200403162120.i2GLKlK01829@djwhome.demon.co.uk>
To: www-style@w3.org

> A way to circumvent this problem would be identifying the minimum 
> version that needs to be supported in order to process the stylesheet.

This suggestion comes up about every three months; please read the

Basically, all the common browsers would probably come out at version
0.0 on a blanket test like this, certainly none will come out better
than 1.0 (screen only).

Even if there were a browser that approached 2.0, the vendor's marketing
department would almost certainly interpret compliance more liberally
than an author would.

CSS represents hints and it is perfectly valid not to implement something,
if it is not practicable to do so on the platform on which the browser

The users can still override any of your rules.

> <link href="mystyle.css" rel="stylesheet" type="text/css" 
> xml:css-version="3.0"/>

This will be interpreted as 0.0 by all browsers that don't implement
your feature.  I'm not sure if browsers will fault the use of
the version in the type attribute or simply ignore it there, as well.

> 2. An at-rule statement in the stylesheet
> @version 3.0;

This is equivalent to version 0.0, except for possibly poisoning the
following sequence of selectors.  In other words it doesn't degrade
gracefully itself.

In my view, the only thing that gets close is an all or nothing 
grouping, but even that is subject to liberal interpretation of 
implementation by the vendor.

PS your email address is broken and the domain is missing the mandatory
Postmaster account.
Received on Tuesday, 16 March 2004 16:20:55 UTC

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