Re: [csswg-drafts] [css-animations-2][web-animations-2] How should AnimationTrigger work? (#12119)

It might be helpful to agree on a set of expectations (prioritized in case some of them are not self consistent) and work through the details of how well each model explains them / requires fewer special cases. E.g. here's some ideas to start:

Of course, existing animations should work as they do today, i.e.
* CSS animations or element.animate or calling play after constructing an animation should play the animation immediately
* canceled or finished animations should have no effect and not be listed in getAnimations

Setting up an animation with a trigger that is not yet active (either via CSS* or element.animate* or the animation constructor and calling play) should result in:
* an animation in its before phase (or after if reversed)
* that will not advance until the trigger is active
* and is listed in getAnimations

\* CSS animations and Element.animate implicitly "play" their animations

If you create an animation with a trigger but don't play it (e.g. Animation constructor), just like with regular animations, it will:
* not be actively producing an effect
* not listed in getAnimations
* not start if/when the trigger condition is active

If you call pause on an animation:
* if it is currently playing, it should pause
* if it is not yet triggered, it should not trigger even if the trigger condition becomes active, until play is called

If you explicitly call play on an animation (this one may be the crux of the differences), but I argue that it should be consistent with implicit play (from CSS or element.animate):
* if play has not yet been called (either implicitly or explicitly), then it should arm the trigger,
* if the trigger was already armed, perhaps it should immediately consider the trigger to have been tripped?

-- 
GitHub Notification of comment by flackr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12119#issuecomment-2842322212 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 30 April 2025 15:11:37 UTC