- From: Robert Flack via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 17:09:53 +0000
- To: public-css-archive@w3.org
Why not though? Is there a reason having it animateable makes the implementation more complex? In https://www.w3.org/TR/web-animations/#not-animatable we say: > Note: Properties are typically excluded from animation because animating them would create excessive complications. For example, properties defining animation parameters are [not animatable](https://www.w3.org/TR/web-animations/#not-animatable) since doing so would create complex recursive behavior. In the past we've defined several properties as not animateable because we didn't see reasons to animate them, and then later reasons to animate them came up and we took compat risk in making them animateable. I'd prefer if we err on the side of everything is animateable unless doing so results in complex recursive behavior. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9619#issuecomment-1823167252 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 17:09:55 UTC