Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#10125 closed feature (wontfix)

delayed mouse event only fires on mousemove (use case: sortable)

Reported by: saeder Owned by:
Priority: minor Milestone: none
Component: ui.mouse Version: 1.10.4
Keywords: Cc:
Blocked by: Blocking:

Description

I thougt it was a good idea to use the option delay: 1000 with my sortable list. Unfortunately the mouse event is only fired after the delay timeout and moving the mouse.

Therefore I change my copy of ui.mouse in _mousedown made the _mouseDelayTimer to call _mouseStart. That way one can change the ghost appearance after the delay.

I suggest this as a standard behaviour.

Change History (3)

comment:1 Changed 5 years ago by Scott González

Resolution: wontfix
Status: newclosed

We're removing the delay option in future versions, so we're not going to change the behavior now.

comment:2 Changed 5 years ago by saeder

Think of mobile, or more generally, touch devices. I'm pretty sure the delay option is needed there. How else would you distinguish between scrolling and dragging and dropping. Certainly I need it now. That's why I fixed the behaviour in copy of the jQuery Framework.

It is indeed confusing when one moves the cursor around and then an action is performed where the mouse cursor is not.

comment:3 in reply to:  1 Changed 5 years ago by saeder

Replying to scott.gonzalez:

We're removing the delay option in future versions, so we're not going to change the behavior now.

Think of mobile, or more generally, touch devices. I'm pretty sure the delay option is needed there. How else would you distinguish between scrolling and dragging and dropping. Certainly I need it now. That's why I fixed the behaviour in copy of the jQuery Framework.

It is indeed confusing when one moves the cursor around and then an action is performed where the mouse cursor is not.

Note: See TracTickets for help on using tickets.