Skip to main content

Search and Top Navigation

#3655 closed bug (invalid)

Opened December 11, 2008 07:51AM UTC

Closed November 08, 2012 08:53AM UTC

Sortable: Connected sortable intersection detection issues

Reported by: wundbread Owned by: wundbread
Priority: minor Milestone: 2.0.0
Component: ui.sortable Version: 1.6rc2
Keywords: Cc:
Blocked by: Blocking:

I have a nested list structure where every list is connectedWith the other lists via:

$("#main .opened > ul").sortable({connectWith: $("#main .opened > ul")})

Sorting within lists is smooth, as it is between 'peer' lists on the same level. Sorting between levels is significantly more difficult. Dragging from parent->child isn't too bad, but from child->parent it take a considerable amount of 'wiggling' before the parent picks up the item.

It behaves pretty much the same in ff3(linux), opera 9.6(linux), ff2(win), and ie6(win).

Attachments (0)
Change History (5)

Changed January 02, 2009 02:20PM UTC by scottgonzalez comment:1

milestone: TBD1.6

Changed March 08, 2009 02:29PM UTC by rdworth comment:2

milestone: 1.71.8

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


Changed October 25, 2012 12:38AM UTC by petersendidit comment:4

owner: → wundbread
status: newpending
summary: Connected sortable intersection detection issuesSortable: Connected sortable intersection detection issues

Thanks for taking the time to contribute to the jQuery UI project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.

Additionally, be sure to test against the git version of both jQuery UI and jQuery to ensure the issue still exists. To get you started, use this boilerplate: the link and click to "Fork" (in the top menu) to get started.

Changed November 08, 2012 08:53AM UTC by trac-o-bot comment:5

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!