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

Re: [css-variables] Resolving cyclical references in a better way (Issue 3)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 6 Sep 2012 11:19:20 -0700
Message-ID: <CAAWBYDB4DVKvYNTiqMmgAe7FeB-Ke9quW6gr7qFTGxi_UMfOVA@mail.gmail.com>
To: François REMY <fremycompany_pub@yahoo.fr>
Cc: CSS WG <www-style@w3.org>
On Thu, Sep 6, 2012 at 2:46 AM, François REMY <fremycompany_pub@yahoo.fr> wrote:
> At this time, inadvertant cyclical references in CSS will result to poor
> results because it marks every custom property invalid, having for
> consequence the invalidation of many other CSS properties at computation
> time, which mean the ‘initial’ value of the property will be used instead.
> A better way to handle cyclical references is proposed in the current CSS
> Custom Properties draft which takes in account the fallback value of the
> broken references to ‘fix’ the issue.

I think you might misunderstand the spec's handling of this case.  The
variables defined by cyclic custom properties are invalid, yes, but
that triggers fallback values if they're provided.

(Note - it would be helpful for you to link your proposal in the
emails that reference it.  It sounds confusingly like you're saying
something about a draft on dev.w3.org.)

Received on Thursday, 6 September 2012 18:20:08 UTC

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