W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [css-variables] Empty variable values?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Sat, 9 Feb 2013 11:29:22 -0700
Message-ID: <CAAWBYDD7PJT+TDG73UHamCOv29b0+acAdFi_qyP+Z=CfbcGs2g@mail.gmail.com>
To: Fran├žois REMY <francois.remy.dev@outlook.com>
Cc: www-style list <www-style@w3.org>
On Sat, Feb 9, 2013 at 11:10 AM, Fran├žois REMY
<francois.remy.dev@outlook.com> wrote:
>> If you want to have a variable be explicitly invalid but still in the
>> OM for some reason, you can explicitly invalidate it with a
>> self-reference ("style.var.foo = 'var(foo)';"). This is a horrible
>> use-case, though - the only difference between it and unsetting the
>> property is that if the property is also set on an ancestor, but you
>> don't want that value and want to instead use fallbacks. I can't see
>> any reason to ever do that on purpose.
>
> Emulating non-inherited properties without using * { var-xxxx: var(xxxx); }

The correct way to do that is to actually add non-inherited
properties, which I intend to add to level 2.

~TJ
Received on Saturday, 9 February 2013 18:30:09 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:05 GMT