Jump to content
Search Community

elegantseagulls last won the day on March 29 2023

elegantseagulls had the most liked content!


  • Posts

  • Joined

  • Last visited

  • Days Won


elegantseagulls last won the day on March 29 2023

elegantseagulls had the most liked content!


Contact Methods

Recent Profile Visitors

7,740 profile views

elegantseagulls's Achievements

  1. Since you're pin contains your next animation, it's not longer tied to a viable scroll position. You might look at this for its "containerAnimation" or "isInViewport":
  2. You have overflow hidden on your html/body, but are trying to use window.scrollTo, which is contradictory. Have you looked at using GSAP's scrollTo functionality/plugin? I also see multiple scroll bars in the CodePen, so I'm guessing that's also causing an issue. For your end value you spelled 'center' incorrectly, and your end value is triggering before your start value the way you have it setup.
  3. #designExt { max-width: 100vw; overflow: hidden; height: 100vh; display: flex; flex-wrap: nowrap; position: relative; } Updating the css to this seemed to work for me, unless I'm misunderstanding your question. You shouldn't need to limit the overflow on the body.
  4. Your fromTo needs more information, but it looks to me like you can just use a to animation for this. Example: gsap.to( ".right-door", { opacity: 0.85, scrollTrigger: { trigger: ".right-door", scrub: true, start: "top top" }, xPercent: -50 } );
  5. Exactly what I was looking for! Thanks!
  6. I think that's just browser behavior for when you remove content in Safari... I'd suggest also manually setting your scroll position immediate after you remove the content.
  7. Removing the button and taking the paused: true off the animation seems to play the animation just fine. The nature of setting things up like this, it's hard for React to know how many children/sub-children there are. That said, we set something similar to this up a long time ago, but I'm having trouble re-piecing it together in my head... this was when we were using pure components and lifecycles instead of hooks.
  8. You can setup animation components and import those into your other components in to avoid repeating code. Also, we've found using https://greensock.com/docs/v3/GSAP/gsap.registerEffect() and making the effects into hooks works pretty well across bigger projects.
  9. Looks like maybe fouc to me? You'll want to set your initial css property to visibility: hidden; Better details here:
  10. Adding ease: 'steps(1)' to your from and to will fix this, otherwise you can change duration to 0 and add a delay.
  11. You shouldn't need to use TimelineLite anymore (as of version 3.0). You can now just use gsap.timeline(). Also, you can write eases as strings now, so no need to import those (unless it's a special ease). More info here:
  12. I cannot replicate with my browsers, but I'd imagine you've got some overflow on another element that's causing the body to try to scroll separately from the scroller in your setup. have you tried removing the overflow-x and overflow-y styles from the .fl-tests class?
  13. You'll want to just add buttons to tween the draggable instance by one snapX... More clarity can be found here: and:
  • Create New...