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

Re: [CSS-Variables] Suggestion of change to time of substitution

From: Tom Potts <karaken12@gmail.com>
Date: Sat, 17 Nov 2012 20:05:00 +0000
Message-ID: <CAF2aeH3UrOZBb5snZWT+AcVnmRZhUy6qZ_xgk-eb8QSsJz+iFw@mail.gmail.com>
To: Fran├žois REMY <francois.remy.dev@outlook.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, CSS WG <www-style@w3.org>
Personally, I think this merits a change in the Cascading and
Inheritance<http://www.w3.org/TR/css3-cascade/> specification.
I think section 3 would need changing to something like

The specified value is found by using the following pseudo-algorithm:
1. If the cascading process (described below) yields a winning declaration,
resolve any property references (see Custom Properties [CSS-VARIABLES]),
  a. if the resolved declaration is invalid {a link the the definition of
"invalid"}, proceed to step 2 as if no declaration had been made;
  b. otherwise, if the value of the resolved declaration is 'inherit', the
inherited value (see below) becomes the specified value;
  c. otherwise, if the value of the resolved declaration is 'initial', the
initial value (see below) becomes the specified value;
  d. otherwise the value of the resolved declaration becomes the specified
2. If the cascading process yields no winning declaration, then
  a. if the property is inherited, the inherited value becomes the
specified value;
  b. otherwise, the initial value becomes the specified value.

I think something like this is necessary: I don't think a change like this
can be made just in the CSS-CUSTOMS module. I guess there should be some
words somewhere to say what to do if the UA doesn't support custom

On 7 November 2012 21:47, Fran├žois REMY <francois.remy.dev@outlook.com>wrote:

> |  they'll get substituted into other properties at
> |  computed-value time, when it's already too late to actually process
> |  them (they're processed in the transition from cascaded to specified
> |  value).
> This is why I changed the wording of my spec to say that reference
> resolution happens just after cascaded time. If you do so, the 'inherit'
> keyword get replaced just before the value computation and, actually, it
> will work as expetected.
> See http://fremycompany.com/TR/**2012/ED-css-custom/#value-**resolution<http://fremycompany.com/TR/2012/ED-css-custom/#value-resolution>
Received on Saturday, 17 November 2012 20:05:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:23 UTC