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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sun, 30 Oct 2011 09:26:39 -0700
Message-ID: <CAAWBYDB_X12U_V8DUXfMb08B8sNaCx5jJhCjb_qBtH0T7VaaWQ@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
On Sat, Oct 29, 2011 at 5:46 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> On 10/28/2011 01:04 PM, Tab Atkins Jr. wrote:
>> On Fri, Oct 28, 2011 at 12:57 PM, Brian Manthos<brianman@microsoft.com>
>>  wrote:
>>> Is this the proposal?
>>>
>>> 1. Bulk edit every property value grammar in CSS3 to explicitly include
>>> the inherit keyword
>>> 2. Add core phrasing that makes it clear that every property should
>>> support inherit unless explicitly specified otherwise
>>> 3. Remove 1
>>> 4. Decide what to do about CSS3 behavior of CSS2.1 properties that don't
>>> have a CSS3 module
>>> 5. Discuss which cases should disallow inherit and update specs
>>> accordingly
>>> 6. [later] Add 'initial' to the phrasing from step 2
>>>
>>> Step 1 is optional if step 2 happens "soon".
>>
>> Step 2, 4, and 6 are already handled in CSS3 Values&  Units:
>> <http://dev.w3.org/csswg/css3-values/#component-types>  and
>> <http://dev.w3.org/csswg/css3-values/#common-keywords>.
>>
>> It would probably be useful to do a thorough search for anything that
>> would run afoul of step 5, but luckily they're pretty rare.  (It only
>> happens when a property accepts an arbitrary user-defined keyword.)
>
> Properties that accept arbitrary user-defined keywords still allow inherit.
> They just don't allow it to be interpreted as an arbitrary user-defined
> keyword.

Right, that's what I meant.  Sorry for being unclear about that.  I
already do this for things like @counter-style.

~TJ
Received on Sunday, 30 October 2011 16:27:28 GMT

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