[web-animations-1] Should updating the timing of an effect update the finished state of its animation?

[cdoublev]

§ Updating the finished state includes this non-normative example:

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 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.

[birtles]

I think this is covered by the model liveness section.

[cdoublev]

Ah, apologize, I missed it... again! This issue is a duplicate of #5526.

I did not considered (again) that AnimationEffect.updateTiming() requires updating the finished state, because it seems to be the only entry point of the programming interface that updates a part of the model that is not the animation object, while the entry points updating it always reference a procedure of the timing model that requires updating the finished state, therefore the model liveness is explicitly specified for them.

[birtles]

No need to apologize! Sorry the spec is not easier to follow!