Sortable: Items cannot be dragged directly into bottom position

Reduced and confirmed against master: http://jsfiddle.net/tj_vantoll/NjBLd/. You cannot drag an item from one connected sortable directly into the bottom position of another. I've played with various configurations of height/padding/margin and the behavior seems to occur regardless.

#9365 is a duplicate of this ticket.

#9370 is a duplicate of this ticket.

Per #9370 this was a regression introduced in 1.10.2.

#9381 is a duplicate of this ticket.

Another good test case from dylanpyle in #9381: http://jsfiddle.net/VNZW8/. It looks like the placeholder is being put in the first position when it should be in the last one.

Guessing this was caused by this commit but haven't confirmed that yet: https://github.com/jquery/jquery-ui/commit/89473f6557662d905a63faa3ae3520bf3715a7e8.

Replying to [comment:6 tj.vantoll]:

Another good test case from dylanpyle in #9381: http://jsfiddle.net/VNZW8/. It looks like the placeholder is being put in the first position when it should be in the last one.

This certainly isn't happening all the time though. My test case and other website with this bug don't place the placeholder in the first position. Are you sure that's a duplicate?

I have a similar issue. I have a sortable parent list that may or may not have sortable sub items. These sub items can be moved from one parent item to another. If you want to move a sub item to an empty parent item you can't without first sorting over other sub items (if there are any). Here's the jsfiddle http://jsfiddle.net/ZwaT3/

I found that the following if statement in the sortable widget _contactContainers function seems to be the cause of the issue.

if(this.currentContainer === this.containers[innermostIndex]) {
     return;
}

(In 10.2 this is around ln 890 in the jquery.ui.sortable.js file and ln 4352 in jquery-ui.js)

This if statement was added by commit https://github.com/jquery/jquery-ui/commit/89473f6557662d905a63faa3ae3520bf3715a7e8 in relation to ticket #8792.

Replying to [comment:8 BenjaminRH]:

Replying to [comment:6 tj.vantoll]: > Another good test case from dylanpyle in #9381: http://jsfiddle.net/VNZW8/. It looks like the placeholder is being put in the first position when it should be in the last one. This certainly isn't happening all the time though. My test case and other website with this bug don't place the placeholder in the first position. Are you sure that's a duplicate?

I'm pretty positive that it has the same root cause (i.e. the same commit caused the issue), but from what you said this does sound like a separate issue. I'm guessing if one is fixed the other will be addressed as well, but to be safe I reopened #9381.

Thanks.

Sortable: Adjust itemWithLeastDistance algorithm in _contactContainers to properly handle dragging items to the beginning and ends of lists. Fixes #9314 - Sortable: Items cannot be dragged directly into bottom position. Fixes #9381 - Sortable: Connected list placeholders have an inaccurate initial position

Changeset: 601ad962e0a417bb369378ed7704a0b493eac365

#9607 is a duplicate of this ticket.

I'm seeing this same behavior as well, and it's very frustrating. Just some encouragement here to let you know this fix is very much anticipated.

Thanks.

#9773 is a duplicate of this ticket.

I found when this bug happened.

In method _contactContainers finding itemWithLeastDistance (closest item from current dragged item) and this.direction (where need set placeholder after or before itemWithLeastDistance).

Reason - wrong direction, because on over sortable first time all inner items have height 0.

Any news on the subject? I'm experiencing this issue, but didn't seem to find an answer to fix it, in the comments here. Anyone knows of an update coming out in a near future - or can direct me to a something that will fix this issue? Thanks in advance.

Replying to [comment:17 dnlmzw]:

Any news on the subject? I'm experiencing this issue, but didn't seem to find an answer to fix it, in the comments here. Anyone knows of an update coming out in a near future - or can direct me to a something that will fix this issue? Thanks in advance.

A fix for this is included in 1.11. You can try out the beta release: http://blog.jqueryui.com/2014/04/jquery-ui-1-11-0-beta-1/

#10055 is a duplicate of this ticket.