Hi all,
I've forked the ScrollTrigger + Locomotive demo linked from your website. The only changes I've made were to add two extra sections to make it longer, and then add the data-scroll-container and data-scroll-section attributes, as is recommended by Locomotive:
To break ScrollTrigger, you can simply scroll through the demo as usual, and then once at the bottom, just resize your browser. (Please ensure that all other sections are outside the viewport.) When you scroll back up to any of the other sections, their ScrollTriggers will be broken and will not play, as if you're not re-entering their section at all. This behavior is reproducible in all scenarios when employing smooth scroll and data-scroll-section.
Calling ScrollTrigger.refresh() from the console will only refresh any ScrollTriggers that are currently within view, rather than refreshing globally as it states it should. I have a hunch that it's related to how Locomotive puts a data-scroll-section-inviewattribute on the relevant section (and makes all others opacity 0 and resets their transform), but that's about as much as I've been able to deduce so far. This has been racking my brain for a couple of days and I would greatly appreciate assistance.
Thank you and sincerely,
C5