Hi there,
Latest days I’ve tested further the animation panel. Here some minor considerations. I’d like to write a more detailed post but I’m finding only now that I’m on holiday a bit of time so:
In the animation panel:
- “bound to trigger” seems gone now. Of course “toArray” is present. How are treated old timelines that use bound to trigger?
- I’m not sure if putting controls to animate width/height/padding/margin is a good idea. Transforms and scale are really more performat.
Page transition: here the situation seems like before at first sight.
- the removal of the trigger selector necessary creating a timeline greatly improves this area. It is really a good move.
- If you have more than one animation the “play on page load” one strangely should be the second one, not the first one (Otherwise it won’t run or the first override it).
- It would be useful to have an option: play on page load and “run only once”.
Due to the complexity of the page transition area I think that I’ll open a ticket. Seeing directly will be easier to understand.
Thanks again for the great v4 that is coming!
Hi Filippo,
thanks a lot for taking the time during your holiday - much appreciated. Point by point:
“Bound to Trigger” is not gone, it only moved and got a clearer name. It now sits directly under the Trigger Selector as “Animate the trigger element itself” and appears as soon as a trigger selector is set. It is the same stored setting as before, and the frontend evaluates it exactly as it did, so existing timelines keep running unchanged - each matching trigger still gets its own animation. “As Array” moved to the Advanced section as “Treat matched elements as array”. Nothing is migrated or rewritten in the background.
About width/height/padding/margin: you are right that transforms are the better choice in almost every case. Those controls are not new though - the panel reads the same control set the old one used, so removing them would break existing timelines. The Transform group is deliberately at the top of the list.
Page transitions: good catch. The entries are set up in the order you listed them, and the “Play on initial page load” state is applied during that setup - so if two entries end up on the same timeline, the later one wins, and an incompletely configured entry can stop the setup for the ones after it. I will take a closer look at both. A ticket with your actual setup would help a lot here, page transitions are hard to judge without seeing the site.
Kind regards
Daniele