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

Re: [css-variables] Resolving fallback-enabled cyclical property references

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 23 Oct 2012 08:25:52 -0700
Message-ID: <CAAWBYDC58EL_WfW8aNJs6NcmAKKfaPz0cZZYEcRmR4SVYZLSYQ@mail.gmail.com>
To: Tom Potts <karaken12@gmail.com>
Cc: Fran├žois REMY <fremycompany_pub@yahoo.fr>, CSS WG <www-style@w3.org>
On Mon, Oct 22, 2012 at 11:36 PM, Tom Potts <karaken12@gmail.com> wrote:
> Very interesting, Fran├žois. I've been thinking about something similar, but
> I wasn't able to come up with a working algorithm. Am I right in thinking
> that this only solves problems where backup values are defined? Or are you
> suggesting that
>    el {
>       my-property-a: no-b;
>       my-property-a: get(my-property-b);
>       my-property-b: get(my-property-a);
>    }
> would also resolve to "no-b" for both properties?

No, the first property gets dropped there as soon as you see the
second, so you're guaranteed to see a cyclic reference there.

Received on Tuesday, 23 October 2012 15:26:44 UTC

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