Ticket #5671 (closed bug: fixed)

Opened 5 years ago

Last modified 21 months ago

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:
Blocking: Blocked by:

Description

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 4.1.249.1036 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.

Change History

comment:1 Changed 5 years ago by rdworth

  • Priority changed from minor to critical
  • Milestone changed from TBD to 1.9

comment:3 Changed 4 years ago by scott.gonzalez

  • Priority changed from critical to major

comment:4 Changed 3 years ago by encoded

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

comment:5 Changed 3 years ago by Isix

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.

comment:6 Changed 3 years ago by garym

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

comment:7 Changed 2 years ago by scott.gonzalez

  • Milestone changed from 1.9.0 to 2.0.0

comment:8 Changed 2 years ago by petersendidit

  • Status changed from new to open
  • Summary changed from Sortable out and over issues to Sortable: out and over issues

comment:9 Changed 23 months ago by doncullen

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.

comment:10 Changed 21 months ago by tj.vantoll

  • Status changed from open to closed
  • Version changed from 1.8.1 to 1.9.1
  • Resolution set to fixed

I'm not sure what fixed this (neither change to Sortable seems relevant  http://jqueryui.com/changelog/1.9.1/), but this issue no longer occurs as of 1.9.1:  http://jsfiddle.net/tj_vantoll/RGeMV/. You can bump the version # back down to 1.9.0 to see the issue.

Note: See TracTickets for help on using tickets.