- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Sat, 11 Nov 2023 10:12:40 +0000
- To: public-css-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-values-5] Clarify not animable `mix()` argument == [`mix()`](https://drafts.csswg.org/css-values-5/#mix) is defined to possibly take arguments that are not animatable. > The `mix()` notation is a `<whole-value>`. Additionally, if any of its `<whole-value>` arguments are [not animatable](https://drafts.csswg.org/web-animations-1/#not-animatable), the notation is invalid. The definition of *not animatable* refers to properties, not values: > The property is not animatable. It is not processed when listed in an animation keyframe, and is not affected by transitions. Are you considering defining property animation types based on their specified value and updating Web Animations accordingly? Do you have an example of a property that is not animatable with some type of value? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9591 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 11 November 2023 10:12:42 UTC