Jump to content
Search Community

dasein

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by dasein

  1. Thank you! I didn't use this exact technique since I couldn't figure out what to interpolate on a duplicate timeline but I was able to use interpolation on something else that did the trick!
  2. Hello! I'm having trouble figuring out how to resume playback of a timeline that tweens ScrollSmoother after it has been paused and position of the scroll position has been updated via manual scrolling. I want the user to be able to play the timeline, but if they pause the timeline and manually scroll to a new position and hit play again, I would like that the timeline plays from the new scroll position at the same speed at which it had left off. As you can see in the codepen, if the user pauses and manually scrolls to a new position and hits play again, they will jump to the position where they hit pause. I've tried several different methods which haven't worked. I'll spare the details of those failed attempts, but to summarize, updating the timeline progress with the scrollsmoother's progress on scrollsmoother updates did not work because there could be more scrolling area on the scroll smoother than there is area on the timeline scroll as well as the fact that the scrollsmoother progress is linear while in my example the timeline progress is not since there are sections of the timeline which scroll at different speeds as you can see in the codepen. Thanks in advance for the help and amazing products!
  3. I'm a bit late to the party here but am now looking up testing solutions for GSAP and can think of at least one good reason to automate tests. I've found that results can be rather inconsistent especially when wrangling Safari. Rather going back and forth all the time to make sure that animated elements are it least in the general area you expect it to be (or that it didn't completely crash the browser on mobile safari), it might be nice to automate these things and be alerted to that effect instead. Right now, it is quite a pain to have to verify any change across several mediums for any change, especially when those changes potentially cause regressions by overloading what some browsers are currently capable of handling.
×
×
  • Create New...