- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Feb 2023 14:16:56 +0000
- To: public-fxtf-archive@w3.org
cdoublev has just created a new issue for https://github.com/w3c/fxtf-drafts: == [compositing-2] Define properties with animation type == [CSS properties from Compositing 2](https://drafts.fxtf.org/compositing-2/#csskeywords) are defined with `Animatable: no`, but [Web Animations 1](https://drafts.csswg.org/web-animations-1/#animating-properties) requires `Animation Type`: > How property values combine is defined by the ***Animation type*** line in each property’s property definition table `w3c/reffy` (spec crawler) does not normalize `Animatable` to `Animation Type` therefore users have to check both `propDef.animationType` and `propDef.animatable`, which is not great. Ideally, I think its value should also conform to the values listed in Web Animations instead of `no`, ie. `not animatable`, but `background-blend-mode` and `mix-blend-mode` could be defined with `discrete`. Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/497 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 February 2023 14:16:58 UTC