Re: [css-variables] Remaining Issues

> 1. Animation behavior.
What about to simply disallow custom properties for animation properties
for now?

> How should the global keyword initial/inherit/default be treated?
I'd say the latter.

> How does 'all' interact with custom properties?
Like it wouldn't be set via a custom property.

Note that these answers are given instinctively since I didn't follow the
earlier discussions about these points.

Sebastian



On 11 June 2013 03:54, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> There are three remaining issues on the Variables spec.
>
> 1. Animation behavior.  Should custom properties animate/transition
> like normal properties (always being unrecognized, so they flip at 50%
> progress), or not?  Fran├žois pointed out that allowing them to be
> animated can produce dependency loops in animations, where the
> animation property itself uses a variable which it animates over.  I'm
> thinking we should disallow animation/transition of custom properties
> - they don't transition at all, and they're ignored in @keyframes
> rules.
>
> 2. How should the global keyword initial/inherit/default be treated?
> Are these more of a language-syntax feature, such that they should be
> obeyed when specified in custom properties, or are they more like
> normal values, such that they become the variable's value?  It seems
> like there may be use-cases for either.
>
> 3. How does 'all' interact with custom properties?  Are they all reset
> as well?  If #2 is decided in favor of treating the keywords as normal
> variables values, how does that interact with this?
>
> ~TJ
>
>

Received on Tuesday, 11 June 2013 05:43:51 UTC