Skip to main content

Search and Top Navigation

#5671 closed bug (fixed)

Opened May 28, 2010 08:05PM UTC

Closed March 08, 2013 03:15AM UTC

Sortable: out and over issues

Reported by: admsteck Owned by:
Priority: major Milestone: 2.0.0
Component: ui.sortable Version: 1.9.1
Keywords: Cc:
Blocked by: Blocking:

The out and over functions of a sortable widget are not called correctly with v1.8.1 when using the connectWith option. Testing with v1.7.2 shows the correct behavior. I tested with Chrome on jsFiddle here. You can switch back and forth and see how things work. It also appears the out function is still being called incorrectly as you can see in the example.

Attachments (0)
Change History (10)

Changed May 29, 2010 08:40AM UTC by rdworth comment:1

milestone: TBD1.9
priority: minorcritical

Changed August 15, 2010 11:44AM UTC by pboyd comment:2

Changed October 19, 2010 03:33PM UTC by scottgonzalez comment:3

priority: criticalmajor

Changed June 24, 2011 09:38PM UTC by encoded comment:4

I've been experiencing the "out" behavior mentioned above, even without connectTo. This might somehow be related to, or a regression of bug #3988.

Changed August 02, 2011 11:48AM UTC by Isix comment:5

I have 3 sortables linked. If I drag the item from the first sortable over the second sortable, the over-event is fired. If I leave the second sortable, the out-event is fired. If I reenter the second sortable, without entering another sortable, the over- and out-events are not fired again.

If I drag the item now (without releasing the mousebutton) over the third sortable. The over- and out-events are fired. If I reenter, the events are not fired.

If I drag now to the second sortable again, now the events are fired again, but only for one time. If I reenter the area of the second, events are not fired.

Now I can enter the third sortable again, and I think you understand, the events are fired only for one time.

So, the events over and out are fired only one time until you enter another sortable.

Changed April 26, 2012 03:14PM UTC by garym comment:6

I've run into the same issue, I wish it was fixed. The link to the 'fix' is broken.

Changed October 11, 2012 02:54PM UTC by scottgonzalez comment:7


Changed November 03, 2012 07:15PM UTC by petersendidit comment:8

status: newopen
summary: Sortable out and over issuesSortable: out and over issues

Changed January 12, 2013 10:08PM UTC by doncullen comment:9

Confirming bug; moving item from list1 to list2 without letting go of drag does not fire sortout event (when it should). Once drop (after dragging from list1 to list2) occurs, sortout fires. Moving item back from list2 to list1 results in sortout event firing as expected.

Fix link cited by pboyd is nonexistent, seems pboyd deleted the fix from github. There is no fix at this time.

Changed March 08, 2013 03:15AM UTC by tj.vantoll comment:10

resolution: → fixed
status: openclosed

I'm not sure what fixed this (neither change to Sortable seems relevant, but this issue no longer occurs as of 1.9.1: You can bump the version # back down to 1.9.0 to see the issue.