Re: [css3-variables] Fallback vs. "invalid at computed-value time"

Le 24/02/2013 01:16, Tab Atkins Jr. a écrit :
> As I said above, implementors purposely didn't want multiple cascaded
> values, so this is the intended effect for level 1.  It is likely that
> authors will end up depending on this property, at least accidentally,
> and so we wont' be able to change it in the future.

That is sad.

Is there an alternative for having similar fallbacks? @supports probably 
works, but it a bit heavy-weight.

-- 
Simon Sapin

Received on Sunday, 24 February 2013 00:20:30 UTC