W3C home > Mailing lists > Public > www-style@w3.org > June 2013

Re: [css-cascade] Naming "value of a declaration", renaming "specified value"

From: Sylvain Galineau <galineau@adobe.com>
Date: Mon, 24 Jun 2013 15:14:14 -0700
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>
Message-ID: <CDEE1187.6949%galineau@adobe.com>


On 6/24/13 2:16 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

>The term "specified value" has always been confusing, because it does
>*not* refer to the value the author specified.  Instead, it's always
>referred to the value that starts the standard value-computation
>chain, at the point where a given element has a value for every
>property.
>
>Ironically, we don't actually *have* a term for the value the author
>actually specified in the stylesheet, or the close-enough concept of
>what CSSStyleDeclaration returns.
>
>Private conversation with dbaron (in #css) led to the following
>suggestions:
>
>1. Use "declared value" for the value of a declaration; that is, what
>is returned when you query CSSStyleDeclaration.  This is not
>associated with any particular element, and may not have a value for
>every property.

+1

>
>2. Drop the term "specified value", and slightly modify Cascade so
>that "cascaded value" fills the role.

+2.

> This just requires us to
>slightly change the verbiage around how we handle the global keywords;
>currently, the "cascaded value" may be empty or resolve to one of the
>global keywords.  We'd change it so that as part of the computation of
>the cascaded value, we guarantee that we fill in a value, and resolve
>away the global keywords.

Not quite sure what this means. Got an example?

>(Our current use of "cascaded value" in the
>spec is unobservable from the outside, and we can just lean on the
>term "result of the cascade" to represent the value that might be
>empty or might be a global keyword.)



Received on Monday, 24 June 2013 22:14:40 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:12 UTC