You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- IMPROVED: SplitText, Draggable, and Observer are all now gsap.context()-aware. So for example if you SplitText within a context and then .revert() that context, the SplitText will also get reverted. And any Observer/Draggable that's created in a gsap.context() will get killed when that context gets reverted.
- FIXED: added MotionPathHelper's kill() method to the TypeScript definitions
- FIXED: if you pause a ScrollSmoother on a mobile/touch device that doesn't use touch events, it could trigger a "click" event when releasing the pointer/touch. See https://greensock.com/forums/topic/34265-scrollsmoother-causes-touch-scrolling-to-trigger-link-click/
- FIXED: in a very unusual scenario, a .fromTo() tween might render incorrectly for one tick. See https://greensock.com/forums/topic/34175-animation-flickering-using-fromto-opacity-transform/
- FIXED: if you animate the scaleY to a different value than scaleX and then subsequently you animate scale (not x or y), it would use the scaleX for the starting value for scaleY too. See https://greensock.com/forums/topic/34300-possible-bug-with-transform-origin/
- FIXED: when the Flip animation is finished, Flip now removes the scale, translate, and rotate inline CSS properties that are added during the flip to prevent CSS rules from contaminating transforms.
- FIXED: in a very rare circumstance if you omit the <meta name="viewport" content="width=device-width, initial-scale=1.0"> in the head on an iOS device, a ScrollTrigger that pins an element that originally had a transform may render it incorrectly. See https://greensock.com/forums/topic/34293-safari-ios-hides-pinned-div-in-odd-pinning-scenario/
- FIXED: of you set allowNestedScroll: true on ScrollTrigger.normalizeScroll(), it wouldn't always work if the event was dispatched by an element inside a container that wasn't scrollable but an ancestor was. Alternate solution: https://greensock.com/forums/topic/32836-scrolltriggernormalizescrollallownestedscroll-true-with-scrollable-div/
- FIXED: if you set a ScrollTrigger's pinReparent to true and resize the viewport while that ScrollTrigger is active, it may render incorrectly. See https://greensock.com/forums/topic/34400-react-useeffect-re-rendering-a-timeline/
- FIXED: if you set gsap.ticker.lagSmoothing(false) the timing mechanism could fail after about 27 hours straight. See https://greensock.com/forums/topic/34544-gsap-3-stops-working-after-2-3-days/
- FIXED: ScrollToPlugin is now ScrollTrigger-aware so that it calls ScrollTrigger.update() after rendering which can prevent slight jumps/flashes when pinning, as described at https://greensock.com/forums/topic/31468-navigation-in-mixed-scrolling-horizontal-vertical/
- FIXED: if you disable() a Draggable instance, its onClick event would still fire. See https://greensock.com/forums/topic/34675-click-event-on-draggable-svg-element-still-fires-after-disable-and-kill/
- FIXED: if you set allowNestedScroll: true in ScrollTrigger's (or ScrollSmoother's) normalizeScroll option, it may not work on horizontally-scrolling elements. See https://greensock.com/forums/topic/34672-scroll-with-trackpad-and-touchpad-on-overflow/
- FIXED: on some Android devices, if you apply snapping to a ScrollTrigger that does pinning, it might occasionally appear to unpin for a brief moment. See https://greensock.com/forums/topic/34703-scrollsmoother-scrolltrigger-snapping-causing-jankiness-in-a-pinned-element
- FIXED: ScrollTrigger.killAll() may leave some instances alive. See https://greensock.com/forums/topic/35012-scrolltrigger-killall-is-buggy/
- FIXED: if you create a fromTo() tween in a timeline that's inside a gsap.context() and you set immediateRender: false on that .fromTo() and then force the playhead to the end and back again, when the context reverts it may render incorrectly.
- FIXED: if you use selector text for a SplitText inside a gsap.context() that had a scope defined, it wouldn't limit the scope accordingly. See https://greensock.com/forums/topic/35061-selector-leak-outside-scope-with-splittext-plugin-inside-gsapcontext-in-react/