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

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

From: Florian Rivoal <florianr@opera.com>
Date: Mon, 07 Nov 2011 11:53:45 +0100
To: www-style@w3.org
Message-ID: <op.v4kojvkl4p7avi@localhost.localdomain>
On Tue, 01 Nov 2011 05:18:23 +0100, Brian Manthos <brianman@microsoft.com>  
wrote:

> Sylvain:
>>
>> [fantasai:]
>> >
>> > On 10/29/2011 11:06 PM, Koji Ishii wrote:
>> > > 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.
>> >
>> > Good idea. I've added this to the module template. Now of course we
>> need
>> > to update all the specs. ;)
>> >
>> This is a good compromise. Avoids repetition but ensures a local
>> reference to the
>> relevant clause from each property definition. +1.
>
> While this would be progress, a hyperlink is a pretty subtle indicator  
> of absence/presence of support for inherit (especially when printing the  
> specification).
>
> Will there be other cues in the formatting to make it not so subtle?

We just got tripped by this lack of explicit listing, and failed to add  
support for inherit to a property that didn't list it explicitly. So this  
is not a theoretical problem.

My personal preference would go to having | <generic-values> added to all  
properties, and linking to the appropriate place. Not mentioning inherit  
and initial would be acceptable as well as long as we're consistent about  
it.

Otherwise, it is just to easy for a reader (author or implementor) to  
assume that the places where it is omitted are intentionally indicating  
that the value is not accepted.

  - Florian
Received on Monday, 7 November 2011 10:54:40 GMT

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