- From: Arron Eicholz <Arron.Eicholz@microsoft.com>
- Date: Wed, 16 Mar 2011 22:27:40 +0000
- To: Anton Prowse <prowse@moonhenge.net>
- CC: "www-style@w3.org" <www-style@w3.org>
On Friday, January 07, 2011 12:46 PM Anton Prowse wrote: > Issue 1: 6.2 Inheritance says: > > # When inheritance occurs, elements inherit computed values. The > # computed value from the parent element becomes both the specified > # value and the computed value on the child. > > This is not the case when the keyword 'inherit' is used, though. In that case, > the specified value is 'inherit', which is never the same as the computed > value. > > Secondly, this section does not actually define when inheritance occurs. > Is that because inheritance /always/ occurs when it can? (That would be > consistent with 6.1.1 which says that the specified value is defined to be the > value resulting from the cascade if it exists, else a value resulting from > inheritance (else...).) In other words, if a property is inheritable, does every > element have an internal property which stores the inherited value, > regardless of whether that value is actually used for the computed value? > > If this is the case, could this be made a little clearer in 6.2? > Thank you for your feedback. The CSSWG has addressed your concerns in the upcoming publication of the CSS 2.1 specification[1]. The CSSWG resolved to use the cascaded value term from CSS3-values. We hope this closes your issue. Please respond before 18 March, 2011 if you do not accept the current resolution. [1] http://w3.org/TR/CSS
Received on Wednesday, 16 March 2011 22:28:14 UTC