The timeline autoplay property overwrites the autoplay property of added animations

[DanKaplanSES]

Describe the bug
When a standalone animation is created with an autoplay: false and duration: 0, its complete callback is never called. But pass the same properties into a timeline add and its complete callback will be called.

I believe this is a bug because none of the other properties I tried were overridden by the timeline.

To Reproduce
Steps to reproduce the behavior:

1. Load this codepen.io: https://codepen.io/Daniel-Kaplan/pen/YzbPZWG?editors=1111
2. Read the console

Expected behavior
The console should print no output because the animations have autoplay: false. You'll notice this is true for the standalone animation at the bottom, but the animations that are added to the timeline get their complete callback called so it prints output.

If you set the timeline's default autoplay to false, the example prints nothing, as expected. I.E.: const tl = anime.timeline({ autoplay: false }); does not print anything to the console, so in some situations, this can be used as a workaround.

Desktop (please complete the following information):

• OS: Win 10
• Browser: Firefox
• Version 125.0.3 (64-bit)

Using anime.js 3.2.2

[different55]

If a timeline is the sequence of a number of child animations, unlike all the other properties it only makes sense for autoplay to be global.

It's not clear what the expected behavior would even be. If a timeline has a number of both autoplay:true and false children, what happens to the timeline when one of the false children is reached in the sequence?

Similarly, it's not clear what should be autoplaying if the timeline is false but some children are true.

And for autoplay false children, individual children can't be accessed, so you can't call play() on them, and it's not clear what it means for the whole sequence when one (or multiple) segments within that sequence starts playing.

Best fix is probably to adjust the documentation so that this behavior is mentioned, because it's definitely the only sane behavior.

[DanKaplanSES]

Best fix is probably to adjust the documentation so that this behavior is mentioned, because it's definitely the only sane behavior.

That works for me as a solution, too.

[juliangarnier]

Best fix is probably to adjust the documentation so that this behavior is mentioned, because it's definitely the only sane behavior.

That works for me as a solution, too.

Fixed in V4 :)