Jump to content
GreenSock

Search In
  • More options...
Find results that contain...
Find results in...

josh-warner

ShockinglyGreen
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

4 Newbie

About josh-warner

  • Rank
    Newbie
  1. I had this exact same error occurring except I was not manually calling .refresh() instead it was being triggered automatically by ScrollTrigger but still throwing an error only on random screen refreshes as above. I updated to the latest version (3.5.1) and it seems to have fixed the issue.
  2. Hey Jack, thanks for the quick reply. Okay that helped me look elsewhere, I have just worked out it was an issue within React not ScrollTrigger. I was using React hooks and needed to update the hook to not run on every render rather only on mount. Thanks again
  3. Hi team, I have an animation which tweens in from the top of the screen on scroll using ScrollTrigger. The issue I have found is if I scroll part way down the page, and refresh the screen, the page loads after the trigger and so the animation is already in its completed state (which it should be) but when I scroll back up to the top of the page past the trigger it doesn't reverse the animation and the element is stuck in its completed state rather than be reverted to where it started from. Couldn't replicate the issue on codepen since you can't refresh the page part way
  4. Cheers @GreenSock can you double check it sent please? Nothing seems to have come through. Thanks again!
  5. Hey @ZachSaucier Yep it seems the 3.3.2 release works fine, do you know where I can download the .tgz version of this release? I am using bonus plugins (installing gsap using npm) and the https://greensock.com/docs/v3/Installation only has the 3.3.1 version available for download. Cheers!
  6. Hi all! I have been upgrading a site to gsap v3 and switching out my ScrollMagic code for ScrollTrigger code (ScrollTrigger btw is amazing so thanks a lot!). I am trying to run a timeline().add() method on the TL to fire a custom function but it refuses to fire unless I add another tween to the timeline like a to() method or the like. Code pen with this issue attached, just curious if I am going about this the wrong way or is there a bug here? I tried using ScrollTrigger.create() directly instead but I had the same issue where it refused to fire my function
  7. josh-warner

    ScrollTrigger

    Yesss can't wait to put this to use! Was getting tired of hacking ScrollMagic to work with React smh
×