Jump to content

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


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

606 profile views

column5media's Achievements

  1. The browser and OS does not appear to matter. The video was shot on Big Sur 11.2.3 with Chrome 91.0.4472.106, but it also occurs on Big Sur 11.4 with Chrome 91.0.4472.114. Here are screenshots of it happening in Windows 10 Pro 20H2 on Chrome 91 (114) and Firefox 89.0.1. And it's not a plugin issue, either, because it was tested with Incognito. I also had coworkers confirm they could reproduce on their machines. I didn't bother screenshotting Edge, but it happened there, too. I haven't tested Safari but will if you think it'll help. Went ahead and tested Safari and had identical issues. Please let me know how else I can support.
  2. Here is one video that shows how positioning gets stuck on resize, then unstuck on resize again. They also do not seem to respect where they should be relative to the document position (i.e. 2 grids from the top, and 3 grids separating one another). Near the end, it also demonstrates how the actual order of the elements changes, with it ending up CAB instead of ABC. reordering_objects.mp4
  3. Thank you for the informative reply. It is very unfortunate that these two libraries cannot play nicely together, but I understand the limitation. I believe I'm going to spend some time hacking away at Locomotive to see whether I can resolve the issue by preventing some of its (perhaps unnecessary) transform resets when objects aren't in view. Hopefully the performance impacts aren't decisively negative. I'll report back if I have any success.
  4. Hi Blake, This is a great demo and would be a lovely replacement for Locomotive, but I noticed I was able to consistently break it on resize, similar to the issue I am having in my thread here. I haven't done a proper investigation as to whether or not they are truly related issues (i.e. ScrollTrigger not being able to detect whether it's in a triggered section and .refresh() only affecting those sections that are in view), but it seemed worth notifying someone about. Let me know if you need me to screen record how I go about breaking it, but the instructions I provide in the linked thread seem to work pretty reliably for me.
  5. 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