Re: [csswg-drafts] [css-animations-2] Composed Animations with existing keyframes (#7574)

> Hmm, if one the positions (`start` / `end`) would be optional, I’d rather make the `end` one optional. Like so:

You're right. It makes more sense to get rid of the end position. Also, the `to` keyword and probably also the `from` keyword I suggested earlier would be misleading in this case.

> Not too sure if any of these should be optional though, as the code above could be interpreted as “run `fadeInDown` from 0% to the end”.

That's a valid point. But making them optional makes the case of contiguous animations easier, which is very common. And it would allow authors to add and remove animations without having to care about their runtime ranges. They would be equally distributed similar to how gradient color stops work.

Just another thought: The fractional unit could also be used here. So this:

```css
@keyframes composed {
  1fr fadeInDown;
  2fr flip;
  1fr fadeOutDown;
}
```

would be equal to this:

```css
@keyframes composed {
  0% 25% fadeInDown;
  25% 75% flip;
  75% 100% fadeOutDown;
}
```

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7574#issuecomment-1208677480 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 8 August 2022 22:20:50 UTC