W3C home > Mailing lists > Public > www-style@w3.org > July 2015

Re: [css-cascade] Clarification in initial value section

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 15 Jul 2015 14:42:15 -0400
Message-ID: <55A6A987.3020403@inkedblade.net>
To: Tom Potts <karaken12@gmail.com>, CSS WG <www-style@w3.org>
On 06/01/2015 05:25 AM, Tom Potts wrote:> Hi, all. I thought there was a typo in the Cascade spec (in the Editors Draft and 
all other versions I could find), but on a
> second look (or actually fifth look) I think it's correct, but misleadingly worded. In 7.3.1 of the Candidate Recommendation
> and the Editors Draft, it states "the property’s initial value becomes its specified value". This is misleading, because it
> could be read to mean that the initial value /is set to/ the specified value, rather than the other way around (certainly this
> is how I read it, even though it makes no sense). The next paragraph states "the inherited value becomes the property’s
> specified and computed values", which is similarly hard to parse.
>
> I suggest the following replacement wording (although I'm sure it can be improved):
> 7.3.1. Resetting a Property: the initial keyword
> If the cascaded value of a property is the initial keyword, the property's specified value is the initial value.
> 7.3.2. Explicit Inheritance: the inherit keyword
> If the cascaded value of a property is the inherit keyword, the property's specified and computed values are the inherited value.

Thanks for your suggestions! Those are indeed better.
I've checked them in. :)

~fantasai
Received on Wednesday, 15 July 2015 18:42:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:18 UTC