W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

[csswg-drafts] [css-variables] Better define animation-tainted's behavior wrt loops (#5867)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Jan 2021 19:42:40 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-785391183-1610566958-sysbot+gh@w3.org>
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-variables] Better define animation-tainted's behavior wrt loops ==
As far as I can tell, it's not currently well-defined what happens if you (1) use `--foo: funky; animation-name: var(--foo);` and then `@keyframes funky {...}` defines the `--foo` property as well.

The algorithm specifies that this causes `--foo` to become animation-tainted on the element, making it revert to its initial value when used in an animation property, but it's only being applied *because of* the previous variable substitution. Does this retroactively wipe out the animation, leaving an animation-tainted property around with no animation to actually taint it? Or is there something else that happens?

Need to test and do some thinking on this. It's not an important case, so the final answer shouldn't matter, it just needs to be well-defined.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5867 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 January 2021 19:42:41 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:38 UTC