Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- FIXED: regression in 3.5.0 caused an error to be thrown in IE10 (related to new TypedArrays support). See https://greensock.com/forums/topic/23156-what-browsers-are-supported-by-gsap-3/ - FIXED: some minor TypeScript definition file improvements - FIXED: if you pin something with ScrollTrigger on a page that initially has NO scrollbar and the contents fill the width, for example, it would end up showing a horizontal scrollbar because the width is set without the scrollbar and then one gets added due to the pinSpacing. So now ScrollTrigger will sense this condition and add overflow-y: scroll to the inline style. See https://greensock.com/forums/topic/25182-scrolltrigger-width-of-page-increase-where-markers-are-set-to-false/ - FIXED: if you set start: 0 on a ScrollTrigger and defined a trigger (which doesn't make much sense since numbers are interpreted as absolute thus there's no point in defining a trigger), it could ignore the start and use the default of "0 100%". - FIXED: in some rare cases if you have a repeating timeline and jump to a certain spot AFTER it has already played once, it could render the child animations in the wrong order. See https://greensock.com/forums/topic/25211-unexpected-behaviour-when-moving-group/ - FIXED: if you have a ScrollTrigger set to pinReparent: true, occasionally it might not render the pinned element in the correct spot after a resize. See https://greensock.com/forums/topic/25150-scrolltrigger-and-mobile-navbar/ - FIXED: animating CSS-related properties to a string with padded zeroes at the end (like x: "20.400") causes those zeroes to be interpreted as units. See https://greensock.com/forums/topic/25226-problem-with-set-position-x-with-svg/ - FIXED: if you have a zero-duration tween in a timeline, then move that timeline's playhead to a place BEFORE that zero-duration tween and then backwards, it might initialize when it shouldn't, potentially leading to the starting values being incorrect. - FIXED: if you pass in a CustomEase that has part of the line extending beyond the final position on the x-axis (EXTREMELY rare), it could return an incorrect final value. - FIXED: if you set a percentage-based max-width or max-height on a ScrollTrigger's pinned element, it may not be applied properly (it becomes a max-width/height of the pin-spacer element). - FIXED: in a ScrollTrigger with a matchMedia() that has a snap applied, if you resize to a different break point and then go back again, the snapping may not work anymore. - FIXED: if you call gsap.timeline().tweenTo() multiple times such that you create multiple tweens that are running simultaneously, you could create a situation where the overlap causes mis-timed rendering if an earlier-created one finishes later. The overwrite is set to "auto" now to avoid that (very rare) scenario. See https://greensock.com/forums/topic/25292-on-click-tweento-label-cancel-current-tween/?tab=comments#comment-122340
- Loading branch information
