W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

Re: [csswg-drafts] [css-animations-2] Specify the interaction between API methods and animation-* properties (#4822)

From: Brian Birtles via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Mar 2020 23:40:51 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-594938523-1583365249-sysbot+gh@w3.org>
> Just to be clear, does this example (from your original post) still pause, but just not set the sticky override?

Yes, that's right. This is purely about the override behavior.

> If the above pauses, the `div.style.animationPlayState` would still resolve to running, so we would have to have some level of stickiness in order to ensure the pause, right?

Right, the proposal is that we use the same "stickiness" for timing properties that map to CSS animation-* properties. That is, once you override them from the API, we ignore the value set via style, even if it changes.

Until I write up the spec text for this (hopefully today), it might be easiest to follow by looking at the patches / tests I just landed for this in [Mozilla bug 1459536](https://bugzilla.mozilla.org/show_bug.cgi?id=1459536).

> Then does flipping it cause the animation to start running?

Flipping it does _not_ cause the animation to start running. Once overridden, always overridden.

GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4822#issuecomment-594938523 using your GitHub account
Received on Wednesday, 4 March 2020 23:40:53 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC