Table of Contents
How to resolve a promise using oncomplete or tween?
– FIXED: The callback methods no longer pass the animation instance as a default parameter when no callback parameters are defined (that behavior was new in v3 and undocumented anyway) – FIXED: endArray wasn’t working correctly. GSAP can now animate numeric arrays directly.
What happens when a tween is created after a tick?
– IMPROVED: if a tween is created after the main rendering loop on a particular tick, it won’t lazy-render (so that things are rendered on the same tick rather than waiting for the next tick which could result in a very brief delay).
When to use oncomplete or tween in cssplugin?
– IMPROVED: GSDevTools allows a linked animation to be reversed manually (via code) – IMPROVED: if a DOM element’s property isn’t found, CSSPlugin will attempt to apply a prefix. – IMPROVED: CSSPlugin better handles tweening to a complex value (like “blur (10px)”) when the initial value doesn’t have matching values (like “none” or “”).
Do you need to use tweenmax in GSAP 3?
Before the release of GSAP 3, TweenMax was the most feature-packed (and popular) animation tool in the GSAP arsenal. However in GSAP 3, you no longer even need to reference TweenMax in your code (although you can because GSAP 3 honors the vast majority of legacy code). We strongly recommend migrating to GSAP 3’s streamlined syntax.
What do you need to know about tweenmax?
What are the methods for stagger in tweenmax?
The old TweenMax stagger methods (from version 1 and 2): TweenMax.staggerTo (), TweenMax.staggerFrom () and TweenMax.staggerFromTo () aren’t even necessary in GSAP 3 because a “stagger” special property can be added to ANY tween, like in the demo below: TweenMax inherits methods from TweenLite and it also has quite a few of its own.