- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Sat, 22 Jun 2024 02:39:27 +0000
- To: public-css-archive@w3.org
> > Yes, CSS animations always allowed animating discrete properties. > > Not always :) It was a resolution we made [in 2012](https://lists.w3.org/Archives/Public/www-style/2012Nov/0261.html). Oh, I didn't know that! The point is that because `transition-property`'s initial value is `all`, we couldn't allow transitions to start animating discrete properties without introducing Web compat issues, hence the explicit opt-in. Animations, which explicitly list the properties to be animated don't have that issue (except in the case of shorthands where the impact is less). > I would _really_ like to avoid adding yet another property for this and find a mechanism for providing property-specific or value-specific params to transitions/animations. It seems there is precedent with `transition-behavior`, so we should just adopt that. If `allow-discrete` is default for animations, it could be part of its initial value, or simply not included at all. > > Web Animations can just define a `behavior` option that takes the same values, no? Yes, absolutely, that's one route for sure. If there's never a need for different animations on the same element to interpolate in different color spaces, another route would be something like SVG's `color-interpolation` and `color-interpolation-filter` properties that would cover all animations on a given element, regardless of the API used to create them. I'm a little less averse to introducing another property for this if that property were to cover all possible future interpolation parameters. "behavior" is a poor name, unfortunately, and I think it would be nice to avoid adding that to the JS API / CSS animations if we can help it. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10469#issuecomment-2183711936 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 22 June 2024 02:39:28 UTC