Skip to main content

Search and Top Navigation

#14594 closed bug (wontfix)

Opened September 22, 2015 10:18PM UTC

Closed September 22, 2015 10:26PM UTC

delay requires additional mouse event to work properly

Reported by: davideanderson Owned by:
Priority: minor Milestone: none
Component: ui.sortable Version: 1.11.3
Keywords: Cc:
Blocked by: Blocking:

the _mouseDown function checks to see if the mouseDelayMet is true, and if not, it sets up a timeout which then sets mouseDelayMet to be true.

However, all that timeout does is set the value to true. The event handling has already completed when it fires, and nothing happens until another mouse event happens, such as a mouse move. Which means, _mouseStart does not get executed if you simply click and hold.

Here is a jsFiddle.

Simply click and hold on an item, and nothing happens. After 1 second, the outline should turn red. However, if you delay for a second, then move the mouse, then the outline changes to red, thus the additional mouse move was required to have the delay work.

Attachments (0)
Change History (1)

Changed September 22, 2015 10:26PM UTC by scottgonzalez comment:1

resolution: → wontfix
status: newclosed

This is not something we're going to change. The delay option is being removed.