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: Thu, 27 Oct 2011 20:40:20 +0200
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: "www-style@w3.org" <www-style@w3.org>
Message-ID: <659ja751d79co4s3i58ca89oummch2b7bh@hive.bjoern.hoehrmann.de>
* Sylvain Galineau wrote:
>One major CSS3 module [1] starts with the following statement:
>
>"All properties defined in this specification also accept the inherit keyword as their 
>property value, but for readability it has not been listed explicitly."
>
>Others, [2][3] include inherit in the syntax definition of each property.
>
>An increasing number of modules appear to do neither [4][5][6] do not. This is causing some 
>confusion as there is no way to tell whether this is deliberate or not. 
>
>My preference is for the simple, unambiguous approach followed by Color [2] and Fonts [3].

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).
-- 
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 Thursday, 27 October 2011 18:40:40 GMT

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