#10125 closed feature (wontfix)

Opened June 23, 2014 10:00AM UTC

Closed June 23, 2014 01:00PM UTC

Last modified June 24, 2014 07:28AM UTC

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

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.

Attachments (0)

Change History (3)

resolution:	→ wontfix
status:	new → closed

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.

Replying to [comment:1 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.