- From: Simon Fraser <smfr@me.com>
- Date: Tue, 12 Apr 2011 17:28:49 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Dean Jackson <dino@apple.com>, www-style@w3.org
On Apr 12, 2011, at 4:49 PM, L. David Baron wrote:
>>
>
> One is when you want some properties to be repeated at multiple key
> selectors. For example, you could traverse the edges of a square,
> clockwise from top left, with:
>
> 0%, 25%, 100% { top: 0 }
> 50%, 75% { top: 100px }
> 0%, 75%, 100% { left: 0 }
> 25%, 50% { left: 100px }
>
> rather than having to write:
> 0%, 100% { top: 0; left: 0 }
> 25% { top: 0; left: 100px }
> 50% { top: 100px; left: 100px }
> 75% { top: 100px; left: 0 }
Nice example!
>
>> If we allow cascading keyframes, it's not obvious that you could use separate
>> timing functions for different properties, since the timing-function property itself
>> would be affected by the cascade.
>
> That depends on how you define the cascading: if you defined it to
> use the last keyframe for any keyframe selector that has the
> property (rather than actually merging the keyframes together) you
> wouldn't have that problem.
But that seems a bit too magic, and different from how cascading normally works.
Simon
Received on Wednesday, 13 April 2011 00:29:20 UTC