Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- NEW: Flip Plugin and CustomEase are now in the public downloads! They're no longer available only to Club GreenSock members. Merry Christmas! Please be sure to get the proper "Business Green" commercial license if you're collecting a fee from multiple users. See https://greensock.com/licensing for details. - NEW: percent-based keyframe syntax, like keyframes: { "0%": {...}, "50%": {...}, "100%": {...} } that acts very similar to CSS keyframes - NEW: Array-based keyframes syntax that lets you animate through various values in sequence, like keyframes: { x: [0, 100, 80, 95, 90], y: [100, 0, 10, 5] } - NEW: Entirely new Flip.batch() functionality for advanced FLIP animations that need to synchronize their steps like getState(), setState(), animate(), etc. - NEW: Flip.killFlipsOf(targets, complete) lets you feed in targets and it'll kill any Flip plugin-based animations of those targets. - NEW: FlipState objects have new methods like .add(otherState) for merging in new data, .compare(otherState) to determine which elements are changed/unchanged/entering/leaving, and clear() - NEW: Flip's "absolute" value was previously boolean, but now you can also pass in an Array of targets or selector text to specify a subset of the flipping elements that should get set to position: absolute. - NEW: Flip recognizes a new absoluteOnLeave: true property that'll result in just the elements that are fed to onLeave() to be set to position: absolute which simplifies exit animations. - NEW: ScrollTrigger instances have a .labelToScroll() method that converts a label in a timeline into the associated scroll position so that you could, for example, perform a scrollTo tween to that spot or jump there. See https://greensock.com/forums/topic/29670-scroll-to-label-with-scrolltrigger/?tab=comments#comment-149550 - IMPROVED: if you do a Flip animation with nested: true and a toggleClass, it will apply that class during the calculations so that it'll accommodate certain layout changes made by the application of that class. - IMPROVED: Flip will overrule max-width/max-height/min-width/min-height values during non-scale Flip animations. - IMPROVED: if you define a toggleClass on a Flip.from() animation, it'll be applied to all the targets (even if they're in the onLeave/onEnter elements) - IMPROVED: if you set gsap.config({nullTargetWarn: false}) it will also affect ScrollTrigger triggers/pins - FIXED: ScrollTriggers that have a containerAnimation value didn't update for the first time until the containerAnimation updated, so in some scenarios it could cause a jump (if the trigger elements were already on-screen horizontally, but out of view vertically) - FIXED: MotionPaths that have an "end" that exceeds 1 weren't calculating it properly (regression in 3.6.0). See https://greensock.com/forums/topic/29643-motionpath-doesnt-end-at-desired-value/ - FIXED: if a ScrollTrigger has a pinnedContainer and the page is refreshed after being scrolled down past the point of pinning, the start/end calculations for that ScrollTrigger could drift. - FIXED: if you use end: "max" on a ScrollTrigger and a subsequent instance pushed the maximum scrollable area larger due to pinning, it's now corrected (pushed further down accordingly). - FIXED: gsap.utils.distribute() may slightly miscalculate the return value if you use from: "start" | "end" | "center" (the range used was about 0.5 off). - FIXED: calling .kill() on the same ScrollTrigger (or its timeline) more than once could inadvertently remove a different ScrollTrigger from the internal list of ScrollTriggers. See https://greensock.com/forums/topic/29973-scrolltrigger-erroneously-killed-when-killing-an-unrelated-timeline-scrolltrigger/ - FIXED: sometimes A ScrollTrigger animation's progress in the snapping onComplete didn't quite reflect the scroll position because some browsers lag in dispatching the "scroll" event. See https://greensock.com/forums/topic/30004-scrolltrigger-labels-onsnapcomplete/ - FIXED: if you pin an element that has a flex-basis that's not auto or a negative "order", it may not pin correctly. See https://greensock.com/forums/topic/30060-pinning-and-flexbox/ - FIXED: if you attempt to rewind an animation to a point BEFORE 0 (its start) and it hadn't rendered once yet, it may skip the render. - FIXED: Draggable's bounds might be 1px off in some rare cases when using an element for the bounds. See https://greensock.com/forums/topic/30161-bounds-changed-after-being-zoomed-inout-scale/ - FIXED: a tween's duration may not get updated correctly in a very rare situation: immediateRender is set to true on a .to() that's in a timeline, and the tween has its duration CHANGED by a plugin/instantiation. - FIXED: if you set a transformPerspective value in the "from" part of a .fromTo() without any unit (like "px"), it could cause the transforms not to be set correctly. - FIXED: regression in GSDevTools 3.8.0 could cause it not to work properly or show the ids in the drop-down list. See https://greensock.com/forums/topic/28706-gsdevtools-animation-ids-not-working/ - FIXED: if you apply a TextPlugin animation in a .from() with BOTH an "oldClass" and "newClass" defined, it wouldn't work properly. See https://greensock.com/forums/topic/30337-textplugin-issue-with-from-and-oldclass/ - FIXED: if you use an ampersand right next to text in a TextPlugin tween, the browser could render it incorrectly. See https://greensock.com/forums/topic/30380-textplugin-issue-with-ampersand/ - FIXED: in some rare edge cases, Flip might miscalculate the positioning of nested elements (when their width/height didn't change, but they're inside transformed elements that did in fact change their visible width/height) - FIXED: worked around an edge case where Flip resizing/repositioning might temporarily introduce a scrollbar that throws off the position calculations due to the scrollbar (which is never seen).
- Loading branch information
