Re: Proposal: version at-rule

 > Alan Plum
 >> In a perfect world stylesheets would degrade nicely if a particular 
rule
 >> or selector was not supported by a browser. In the real world some 
rules
 >> build upon each others, sometimes older rules build on newer ones to 
be
 >> interpreted even.
 >>
 >> A way to circumvent this problem would be identifying the minimum
 >> version that needs to be supported in order to process the 
stylesheet.

 > David Woolley
 >> 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
 >> runs.



Sorry, I think Alan Plum had a point.

Origionally CSS worked well with


     <style type="text/css">
     </style>


then V2 came out with a method to hide this new CSS from old "V1 only" 
browsers, which was


     <style type="text/css">
	@import "file.css";
     </style>


so what happens with V3, another way to hide the CSS from V2 browsers?

why not make a 3rd and final rule which hides the CSS from both V1 and 
V2 compliant browsers which includes a version number?


 > David Woolley
 >> 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.


Granted it does not ensure that all the browsers will have full 
compliance, but thats another story. At least by putting in a version 
number it means that future browsers wont bother trying to understand a 
CSS rule that it just cant do.

Received on Wednesday, 24 March 2004 17:06:32 UTC