[Snyk] Upgrade gsap from 3.11.3 to 3.11.4

[snyk-bot]

Snyk has created this PR to upgrade gsap from 3.11.3 to 3.11.4.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.
• The recommended version was released 22 days ago, on 2022-12-22.

Release notes

Package name: gsap

• 3.11.4 - 2022-12-22
  

  • 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 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/

• 3.11.3 - 2022-10-04
  

  • IMPROVED: if you use ScrollTrigger to pin something inside a pinnedContainer (and both have pinSpacing), it'll now adjust the padding/sizing of that pinnedContainer's pin-container element. So nested pinning has better support now.

  • IMPROVED: Previously, MotionPathHelper would only set the pathColor, pathWidth, and opacity if the path that was defined wasn't an svg (if it created a new one), but now it'll honor those properties even if you're using an existing path. See https://greensock.com/forums/topic/34009-arguments-in-the-motionpathhelper-function-are-ignored/

  • IMPROVED: added a console.warn() for when you forget to define a "content" element for a ScrollSmoother.

  • IMPROVED: MotionPathHelper is gsap.context()-aware and has a kill() method for better management.

  • FIXED: regression in 3.11.2 that could cause a .fromTo() tween to render its starting values immediately after .revert() is called. See https://greensock.com/forums/topic/34016-fromto-not-reverting-inline-styles-as-expected/

  • FIXED: if you set a pin value in a ScrollTrigger and fail to set any pinSpacing (true or false) and the pin element's parentNode is NOT a valid Element, it could throw an error. See https://greensock.com/forums/topic/34021-pinned-element-using-scrolltrigger-breaking-the-flow-on-litdev-app-error-failed-to-execute-getcomputedstyle-on-window-parameter-1-is-not-of-type-element

  • FIXED: if ScrollTrigger.refresh() is called when a ScrollTrigger is pinned and the scroll position is not at the very top/left, it could render that pinned element incorrectly.

  • FIXED: When calling ScrollTrigger.refresh(), it may (in certain circumstances) cause ScrollSmoother to jump to the top. See https://greensock.com/forums/topic/33877-scrollsmoother-scrolling-to-top-with-scrolltriggerrefresh/

  • FIXED: if you enable snapping on a ScrollTrigger and have scroll-behavior: smooth on the scroller, it may not settle properly. 3.11.3 sets scroll-behavior to auto automatically in that condition now.

  • FIXED: if you call setPositions() on a ScrollTrigger that pins and has pinSpacing, it'll adjust the pin spacer's height/padding accordingly rather than just changing the start/end.

  • FIXED: in 3.10.0, ScrollTrigger switched to waiting for a requestAnimationFrame() tick to update after a "scroll" event, but newer version of Safari repaint earlier which could lead to things looking jerky in certain cases, so we switched back to immediately updating ScrollTrigger on every "scroll" event. See https://greensock.com/forums/topic/34062-greensock-scrolltrigger-animation-jumping-when-scrolling/

  • FIXED: in some rare cases, a ScrollSmoother-based page couldn't be scrolled all the way to the bottom. This is usually related to nested pins. See https://greensock.com/forums/topic/34056-nested-pins-dont-work/

from gsap GitHub release notes

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs