W3C home > Mailing lists > Public > www-style@w3.org > July 2001

Re: CSS1 compliance/support (was Re: @version rule)

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 30 Jul 2001 19:06:44 +0200
To: Ian Hickson <ian@hixie.ch>
Cc: Tantek Celik <tantek@cs.stanford.edu>, Jeffrey Yasskin <jyasskin@hotmail.com>, <www-style@w3.org>
Message-ID: <574bmtcc3jvle6hto5e7aos71aan2nuq3n@4ax.com>
* Ian Hickson wrote:
>>> IE6/Windows has full CSS Level 1 compliance, just as IE5/Mac did when
>>> it shipped over a year ago,
>>
>> As of build 2479 it doesn't support e.g.
>>
>>   option { text-align: right }
>
>In all fairness, there is nothing in CSS1 (CSS2) that says that CSS
>applies to form controls. That any style applies to form controls is a
>matter of debate, and at best a convention.

Form controls are elements and if CSS says, something applies to all
elements and doesn't explicitly exclude anything CSS1 applies to form
controls; If some user agent developer considered this question and
decided, that CSS doesn't apply to form controls, _no_ properties apply
to form controls and some.

>> Mozilla 2001071004 does, but only in the pulldown menu, the current
>> selection is still left-aligned,
>
>Whether those two locations are the same element is even more open to
>debate. Nowhere else in CSS can a single box appear in two places at once.

If they are the same element, current behaivour is wrong. If they are
not the same element, current behaivour is wrong, since the element
isn't styled but the newly generated box.

>> Both don't support borders for the tr element, while CSS Level 1 says,
>> it applies to all elements
>
>Again, in all fairness, if a UA is to support CSS1, then it is the subset
>of CSS1 that is in CSS2 that should be implemented.

But that'd be nothing I'd call "full support" but rather
"compromised support".

>Thus, tables should be considered out of scope of CSS1.

Same as above. If they support some features, they must support all
mandatory features.

>Oops, thanks for pointing that out. Regarding whether it's a change or an
>error, the distinction is simple: changes are informative, corrections to
>known errors are normative.

That's exactly the reason why I want it to be a change.
-- 
Björn Höhrmann { mailto:bjoern@hoehrmann.de } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/
Received on Monday, 30 July 2001 13:07:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:10 GMT