Drag events supersede click events

[rickghome]

Bug, documentation issue, user error?

I have an element that may become 'active' if clicked by the user. I also want to allow that element to be draggable. Currently, it seems that drag events are superseding click events (and in this case, impedes them, regardless of binding order). It's essential to my user experience that click events precede drag events. I'm guessing this isn't an edge-case.

[tsov]

I can reproduce. You could use the delay option to delay the drag action (for now). It works for Draggable, Sortable, Swappable and Droppable.

new Sortable(containers, {
  delay: 200,
});

// or

new Draggable(containers, {
  delay: 200,
});

This is not ideal nor obvious. Will look for a better solution 👍 thanks for reporting

[rolandasb]

I have the same issue.

Adding delay helps with clicking, but if I try to drag without waiting a bit, I get strange "ghosting" effect, where mirror element gets stuck to the cursor and does not disappear.

Here's gif: https://i.imgur.com/b0zwVkk.gifv

[tsov]

@rbarysas yes, this seems to be an issue with the current mouse sensor, it needs to prevent native drag elements (images and links) if the delay is bigger.

This is fixed with a general sensor refactor for the upcoming v1.0.0-beta.3 release, commit is here: 7432c9a

I will leave this open until we release the new beta.

[rolandasb]

This is awesome. Thanks for the work! 👏

[tsov]

@rickghome can you confirm if your problem persists in the new beta release?

@rbarysas your issue should be fixed now!

[rickghome]

Will try today.

…

Sent from my iPhone

On Nov 1, 2017, at 6:55 AM, Max Hoffmann ***@***.***> wrote: @rickghome can you confirm if your problem persists in the new beta release? @rbarysas your issue should be fixed now! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[rickghome]

This solves the problem. Closing this bug. Thanks for your hard work!