Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: greensock/GSAP
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 3.14.1
Choose a base ref
...
head repository: greensock/GSAP
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3.14.2
Choose a head ref
  • 1 commit
  • 141 files changed
  • 1 contributor

Commits on Dec 12, 2025

  1. 3.14.2 

    - IMPROVED: When a new SplitText instance is created, it will now check to see if any of the targets were already split as a part of another SplitText instance and if so, it'll restore the original content first in order to avoid duplicate splitting. This is not the same as calling revert() on the original/competing SplitText instance because it very well may target many other elements that shouldn't be reverted. It won't affect the isSplit state of the original/competing SplitText instance either. If you prefer to allow the duplicates, you can now set overwrite: false on the SplitText config object.

- IMPROVED: SplitText recognizes Arrays populated with selector text like [".split-1", ".split-2", ".split-3"], although honestly it's cleaner to just do one combined selector text string like ".split-1, .split-2, .split-3". We just wanted to make it backwards compatible with what has historically worked in GSAP.

- FIXED: the ESM version of SplitText distributed via NPM had a compiler-introduced issue that could cause character splitting to produce EMPTY elements. Regression since version 3.14.0. See #636
    @jackdoyle
    jackdoyle committed Dec 12, 2025
    Configuration menu
    Copy the full SHA
    e830e8f View commit details
    Browse the repository at this point in the history
Loading