- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 6 Sep 2012 11:19:20 -0700
- 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.) ~TJ
Received on Thursday, 6 September 2012 18:20:08 UTC