Jump to content
GreenSock

Pixouls

ShockinglyGreen
  • Posts

    5
  • Joined

  • Last visited

Everything posted by Pixouls

  1. Hi Corvinius, sorry for the delayed response. Unfortunately, we had a few fringe device-specific issues we couldn't get around and dropped the draggability. Hope you have better luck!
  2. Hello GreenSockers! We're looking for an ongoing GSAP specialist to help elevate our projects. From the immediate need, to larger projects we are starting in Nov/Dec. Some pretty rad stuff like a music festival, custom luxury furniture maker, go-kart/ax-throwing venue, etc. Lots of potential for creative design/animation solutions. We understand an individual with this skillset is a hot commodity, so we're willing to pay the right person what they're worth. We'd love to see examples of work if you're interested. Thank you! - Ryan
  3. Okay, thanks again for your help. Looking at this a bit more, I agree with you on the necessity of the overwrite because I'm not really seeing a way around that. I may end up going that direction.
  4. Thanks for your reply and suggestions, Zach! Much appreciated. Those changes have brought me very close to a solution. On touch devices, I am still having a few issues, however. Basically, if the Draggable section is part way in the viewport, and the user tries to grab it and scroll back up, Draggable events are firing and the user can't really scroll up normally. I messed around with a few options using the deltas and Draggable.enable()/disable(), but can't quite get it - basically I would need a way to disable Draggable if the user is scrolling vertically. As a side note, I did have to remove the overwrite: 'auto' on the updateProxy function or else that will kill the inertia movements. And related to that, when inertia movements are still going and a touch user tries to grab the screen to stop, a bunch of flickering starts happening as the native scroll position and the inertia movements are fighting. I suppose this is where the overwrite would come in handy, but I would really like to have the inertia preserved if possible - do you happen to have any additional ideas on that? Thank you again for your help!
  5. Hello all, I've recently been working a site that is going to function with a mix of horizontal scroll sections setup with ScrollTrigger, and then other sections with regular vertical scroll. To allow for horizontal swiping on touch devices, I've also integrated Draggable in a similar method as as outlined in the thread linked below. ("horizontal scroll trigger -- tablet / mobile") However, I've run into one major issue on touch devices. After hitting the end of the horizontal scrolling section, the user sees that the screen starts to scroll vertically. At this point, if the user starts vertical scroll on the draggable area starts fighting with Draggable. Additionally, if the user gets past that and into the normal, vertically scrolled content below, the user will have a hard time scrolling back up if they swipe on the section that is setup with Draggable. Basically, the transition between Draggable/horizontal scroll and normal, vertical scroll is the crux of the issue here - and they will fight each other at the transition point. On desktop you can see this somewhat by dragging past the first section, getting toward the end of the first section, then scrolling down a bit. If you drag on the top section while still visible, it will "jump" you back up to previous scroll position - I believe something like that is causing a conflict worse than a jump on a touchscreen. Does anyone have any ideas on how to make these two play together better? I've also tried having the browser watch the ScrollTrigger position and run disable()/enable() on Draggable but that somewhat locks the user out of the vertical scrolling section if they are swiping slowly and without enough throw/momentum for them to see the content below. Thank you!
×