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

Re: [css21] Revising the definition of the 'inherit' keyword

From: Leif Arne Storset <lstorset@opera.com>
Date: Fri, 25 Nov 2011 14:25:38 +0100
To: "www-style list" <www-style@w3.org>
Message-ID: <op.v5h7k0l8tmo5g6@localhost.localdomain>
Tab Atkins Jr. <jackalmage@gmail.com> skreiv Sat, 19 Nov 2011 01:30:29  
+0100

> Sveral telcons ago we discussed the definition of the 'inherit'
> keyword in the 2.1 spec, and agreed to change it to be better in line
> with what CSS3 Cascade says.  Here's my attempted edit:
>
> In 6.1.1, change the ordered list to:
>
> 1. If the cascade results in a value other than 'inherit', use it.
> 2. Otherwise, if the property is inherited or the cascade resulted in
> the value 'inherit', and the element is not the root of the document
> tree, use the computed value of the parent element.
> 3. (unchanged)
>
> In 6.2.1, change the first paragraph to:
>
> Each property may have a cascaded value of 'inherit', which means
> that, for a given element, the specified value of the property is the
> computed value of the property on the element's parent.  If 'inherit'
> is given as a value to a shorthand property, it has the same effect as
> specifying 'inherit' for all of the longhand properties that the
> shorthand represents (even if the combined computed values of the
> longhand properties end up being an invalid value for the shorthand).

Please do this. The current paragraph has caused me some confusion (and  
did not help the learned people I asked to explain).

-- 
Leif Arne Storset, Opera Software
Layout  Developer, Oslo, Norway
Received on Friday, 25 November 2011 13:26:16 GMT

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