[csswg-drafts] [web-animations-1] Should updating the timing of an effect update the finished state of its animation? (#11490)

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [web-animations-1] Should updating the timing of an effect update the finished state of its animation? ==
[§ Updating the finished state](https://drafts.csswg.org/web-animations-1/#updating-the-finished-state) includes this non-normative example:

```js
var animation = elem.animate({ left: '100px' }, 2000);
animation.playbackRate = 2;
animation.currentTime = 1000; // animation is now finished
animation.effect.updateTiming({ iterations: 2 }); // animation is no longer finished
```

It seems that `effect.updateTiming()` **synchronously** changes the finished state of its associated animation, which seems unspecified in its own [procedure](https://drafts.csswg.org/web-animations-1/#update-the-timing-properties-of-an-animation-effect) and in *§ Updating the finished state*:

  > The crossing of this boundary is checked on each modification to the animation object [and also] as part of the update animations and send events procedure. [...]

Perhaps it could be explicitly noted/specified? Unless I am missing something. I cannot find anything else related in the spec, whereas the association between a timeline and animations, and between an animation and effect, seems to be more explicitly defined.

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


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

Received on Monday, 13 January 2025 13:04:16 UTC