- From: Mark Hicken via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jan 2022 23:54:09 +0000
- To: public-css-archive@w3.org
Can anyone think of a case where you would actually want to build your `@keyframes` out of order? It seems odd to me that, we would need to support that. I'm sure some people are doing it because it's been allowed in the past, but it seems like a very strange practice to me. The animation has to execute in a specific order so why not expect the definition/input in the same order? I would suggestion having a look at how [GSAP](https://greensock.com/understanding-keyframes/) and [AnimJs](https://animejs.com/documentation/#animationKeyframes) handle keyframes. These are just a few examples. Having used many different animation libraries over the last 20 years, I'd really love to see CSS come closer to their syntax. It's way more flexible for defining where you want different easing types and durations to occur, how long your overall animation should run and for interrupting animations and changing paths to a new animation midway through. I don't want to blow up the scope of this issue. I think the `via` keyword is a great idea, but it leads me to think that the current `%`-based syntax is less than ideal. Perhaps we need a completely separate "sequential keyframes" syntax? -- GitHub Notification of comment by markhicken Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6151#issuecomment-1007023146 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 January 2022 23:54:11 UTC