W3C home > Mailing lists > Public > www-style@w3.org > October 2011

Re: [css3-*] Defining support for the inherit keyword

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Fri, 28 Oct 2011 15:53:27 +0200
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Sylvain Galineau <sylvaing@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <vncla7lauos18scnhbfj9ie7gm02vr94e8@hive.bjoern.hoehrmann.de>
* Tab Atkins Jr. wrote:
>On Thu, Oct 27, 2011 at 11:40 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
>> This is likely another consequence by relying on CSS3 modules in some
>> places while relying only on CSS21 in others as CSS21 lists it for each
>> property. For CSS3 the idea was that there would be other values that
>> can be used for all properties like 'initial', 'calc', 'attr', and if
>> they are listed for each and every property the grammar becomes indeed
>> unreadable. There could be a compromise to list, say, <generic-values>,
>> but that would not necessarily lead to less confusion (as there would
>> not be a single place that fully expands the macro at the moment).
>
>Note that calc() and attr() don't have a problem here - they always
>resolve into an already-known type.  It's just the global keywords
>that need a special call-out somewhere.

The only reason they have less of a problem in this regard is that they
are not notably inconsistently listed. That they resolve to something
that is allowed where they can be used doesn't affect where they can be
used.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Friday, 28 October 2011 13:53:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:45 GMT