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

On Monday 2013-06-24 14:16 -0700, Tab Atkins Jr. wrote:
> 2. Drop the term "specified value", and slightly modify Cascade so
> that "cascaded value" fills the role.  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.  (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.)

Why do we need a term for the cascaded value with empty cases filled
in?  Why not just have the term "cascaded value"?


𝄞   L. David Baron                  𝄂
𝄢   Mozilla                    𝄂

Received on Monday, 24 June 2013 21:33:07 UTC