Jump to content

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


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Newbie

About Nielsd

  • Rank
  1. Jack, Zach and the rest of the team! Thank you very much! It works perfectly 😀
  2. Hello Zach, thank you very much for your quick response. This feature looks perfect for me and I think, this is necessary for a perfect responsive behavior. There is one thing in your example, which I would wish: If you scroll down to the end of the page, and make the size change, I thing, it would be perfect, to stay at this position. In your case, it jumps back to the start position of the page. I'm looking forward, to work with your solution. This looks very easy to handle ScrollTrigger with different instances in different screens sizes. Thank
  3. Hey, step by step, I figure out, how this fantastic plugin works, but there is one thing, I'm not understanding: The goal is, to make two different instances, which means, when the viewport is wider than 992px, it should load the instance for big screens. When it comes to smaller viewports (on resize), it should kill the actual instance and init a new one for smaller Screens. And that works perfectly with kill(), clearProps and then new init. But it works only on resize, when my scroll position is within the start and endpoint of the first screen instance (isActive).