- From: Håkon Wium Lie <howcome@opera.com>
- Date: Mon, 5 Aug 2002 14:16:19 +0200
- To: Tom Gilder <tom@tom.me.uk>
- Cc: www-style@w3.org
Also sprach Tom Gilder:
> > http://www.w3.org/TR/2002/WD-CSS21-20020802/
>
> While I feel that incorporating errata and cleaning up the specification is a
> good thing, I'm not too sure about this practice of removing properties and
> values.
> Could someone possibly clarify the reasoning behind the major changes?
We've tried to argue for why this is a good thing in:
http://www.w3.org/TR/CSS21/about.html#q1
> After all, isn't the idea of CSS to be as backwards-compatible as possible?
Indeed. And, due to the forward-compatible parsing rules, a style
sheet containing e.g. this rule:
@page {
marks: crop;
}
will be treated exactly the same way as before, since no browsers implement it.
> To
> me, it doesn't make sense removing things simply because they haven't been
> widely implemented yet.
The features will still be described in CSS 2.0 (which continues to be
available), and in CSS 3 (if enough people thik it's valuable
functionality for the future).
-h&kon
Håkon Wium Lie cto °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Monday, 5 August 2002 08:23:29 UTC