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

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

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Sun, 30 Oct 2011 02:06:54 -0400
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0CF961FD6E@MAILR001.mail.lan>
What about making "Value:" label to a hyperlink to the section describing how to read the value of the row?

It might help people like me who just skips introductions and wonders what "||" means or if 'inherit' is supported without sacrificing readability.


-----Original Message-----
From: fantasai [mailto:fantasai.lists@inkedblade.net] 
Sent: Sunday, October 30, 2011 2:47 PM
To: www-style@w3.org
Subject: Re: [css3-*] Defining support for the inherit keyword

On 10/29/2011 05:43 PM, Bjoern Hoehrmann wrote:
> * fantasai wrote:
>> I agree with bzbarsky, and that's why my preference is for each 
>> module to define it in the values and interactions section at the top.
> Just to be clear, are you saying each of the dozens of modules should 
> explicitly say "inherit" and "initial" and so on are implied, or would 
> it be sufficient to have, say, some meta-module on how to read the 
> many modules that defines this which is then referenced from the modules?
> Say a module that define the Value lines along with what `||` and `&&` 
> mean, that says "inherit", "initial", etc. are for all properties? And 
> would it be necessary to make this explicit via some "<generic values>"
> macro?

No, I'd do what I'm doing for values in general: define how the module interacts with features in 2.1, and then explain and allow that the combination with other modules may modify this. For example, implementing both css3-background with css3-values will allow 'initial', in addition to 'inherit', on all the background properties.


Received on Sunday, 30 October 2011 06:07:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:06 UTC