Search the Community
Showing results for tags 'startdrag'.
Found 3 results
-
Hey guys, it's Beholder4096, back again with another obscure bug. This time, the mind-boggling infestation here has taken me to discover two possible ways this bug can be demonstrated, so please bear with me.. I have an object (green in the CP example) which I need to make draggable, after user clicks another object, that is overlapping it (yellow in the example). When the overlapping yellow box on top is clicked, the draggable instance of green is created and green becomes draggable. So far so good. However, if I rerun the example and click the yellow and hold mouse button without movement and then release, the onClick of the draggable object doesn't fire! (all other events do fire, even onDragEnd() even though we were not dragging). I know it looks like it's for obvious reason.. But this behavior makes UI extremely inconsistent in my use case where I am very depending on this to work! Here the user can either (1) click the yellow overlapping object and release immediately (and the green object runs the onClick as it should) or the user can (2) click the yellow, hold the mouse for dragging and drag the green object to the destination. I have noticed that the exact same bug happens when clicking ONLY green object and releasing it without movement, but only when the Draggable.create() code is in the inline javascript onmousedown event. Please refer to the CP example where I have implemented both ways the bug can show. I must stress all of the other draggable events run ok, even the onPress event, which is also quite illogical since when I click the yellow box I never pressed on the green. And in the case of inline-js, I literally click the green and onPress registers but onClick doesn't work. While onDragEnd fires as well even though I totally didn't drag, just clicked. Aah, these crazy bugs, how come no one ever notices them? Please, PLEASE fix this as I would have to do a super-crazy workaround if the 2-box overapping scenario didn't work as it should. tl/dr: Click yellow box or green box. Do not drag. What happens: pretty much nothing, just draggable element gets to the front. What is expected: the onClick event of the draggable green box should fire and show alert. -
Hi all, I've been using GSAP for a while now and frequently browse the forums for advice/tips. The GSAP team makes amazing products and I couldn't be happier with them. Thanks for all the great work! Recently I've been having a lot of fun with the Draggable utility, but just ran in to a couple of problems today within the Chrome browser on Android. I would like to start dragging my Draggable when a separate "anchor" element outside of the Draggable is dragged (touchmove'd) left or right. Kind of like a "hotspot" to start the dragging action. For reasons unknown to me, the following codepen does not work properly. However, if I change all "touchmove" listeners to "mousedown" listeners, the codepen behaves as expected when using a mouse. Full disclosure: it's actually a different issue I was trying to resolve regarding the way Chrome handles touch events vs pointer events when I ran into this little stumbling block. I'm sure that my issue here is something small/silly. Thanks!
-
Draggable. Custom startDrag(). Cant get it work for touch devices
sumimasenga posted a topic in GSAP
Hi! I am building a global velocity tracker that runs as soon as you move your mouse or touch. Im using the Draggable plugin where I call the startDrag method in a mousemove touchmove jquery callback and passing the corresponding event to the startDrag method. Everything is working fine on a computer but when using a touch device it doesnt work. Like if the startDrag never is called. Can you see if I have missed something... I have tested with ipad air 2, ipad air mini, iphone 4s all with ios 8.1 and its not working. Check out the codepen. Thanks for this great library!! //Robert
