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

Re: Adding a font to the current stack (smarter fallbacks)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 11 Jan 2012 13:49:30 -0800
Message-ID: <CAAWBYDDTsAG6i=c5JCQi_N7qYCgUrqx4nfNn8bNvMpj5PSQ1sQ@mail.gmail.com>
To: Fran├žois REMY <fremycompany_pub@yahoo.fr>
Cc: Charles Pritchard <chuck@jumis.com>, Matthew Wilcox <elvendil@gmail.com>, www-style@w3.org
On Wed, Jan 11, 2012 at 1:36 PM, Fran├žois REMY
<fremycompany_pub@yahoo.fr> wrote:
> Yes, that's a common problem. Filters suffer from the same issue. Transforms
> too. An idea would be to allow a new syntax that extends inherit. However,
> allowing "inherit" anywhere in a value is too complex, and it's a breaking
> change.
>
> Two options comes in my mind:
>
> (1) Use "inherit" as a special variable :
>
> .translate100 { transform: translate(100,100), var(inherit); }
> .zoom1 { transform: scale(1.1), var(inherit); }
> // or whatever the variable syntax may be
>
> (2) Use a special "inherit" function that can takes the place of any value :
>
> .translate100 { transform: inherit(translate(100,100), ...); }
> .zoom1 { transform: inherit(scale(1.1), ...); }
> // or any symbol that could replace the ...


Again, inherit is *not* what you want.  You don't want the current
inherit behavior in any way, or even to invoke the *idea* of
inheriting.  This is about manipulating the *current* cascaded value,
not your parent's value.

~TJ
Received on Wednesday, 11 January 2012 21:50:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:48 GMT