- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Aug 2021 19:59:14 +0000
- To: public-css-archive@w3.org
Okay, this ends up getting resolved with <https://github.com/w3c/csswg-drafts/issues/411#issuecomment-890081098> as well. * the animation properties resolve their variables in an early pass, before animations are applied (by logical necessity) * if those custom props are then set by a running animation, it's fine, it just doesn't have any effect on the animation properties referencing them, since *they* were actually referencing a previous version of the definition that didn't involve any running animations. * animation-tainted still lets us prevent running animations from smuggling animation into non-animatable properties, like 'display' So as soon as Animations defines its model wrt computed-value dependencies better, reasonable behavior for this case falls out, and I don't need to do define anything else. 👍 -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5867#issuecomment-891292843 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 August 2021 19:59:16 UTC