Opened 14 years ago
Closed 10 years ago
#4425 closed bug (notabug)
Sortable: Connecting a Sortable via tabs fails when using a sortable(helper: function(...){...})
| Reported by: | lathan | Owned by: | lathan |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.0.0 |
| Component: | ui.sortable | Version: | 1.7.1 |
| Keywords: | sortable tabs helper | Cc: | |
| Blocked by: | Blocking: |
Description
When connecting several sortable lists over a tab (using the helper init option to set a different helper), after the tab draggable drop event fires, the sortable handler reverts the element back to the list.
This bug is very similiar to ticket 4088. http://dev.jqueryui.com/ticket/4088
Change History (7)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
| Milestone: | TBD → 1.7.2 |
|---|
comment:3 Changed 14 years ago by
| Milestone: | 1.7.2 → 1.8 |
|---|
comment:4 Changed 10 years ago by
| Milestone: | 1.9.0 → 2.0.0 |
|---|
comment:5 Changed 10 years ago by
| Owner: | set to lathan |
|---|---|
| Status: | new → pending |
| Summary: | Connecting a Sortable via tabs fails when using a sortable(helper: function(...){...}) → Sortable: Connecting a Sortable via tabs fails when using a sortable(helper: function(...){...}) |
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: http://jsfiddle.net/ZgAqH/Open the link and click to "Fork" (in the top menu) to get started.
comment:6 Changed 10 years ago by
| Status: | pending → new |
|---|
The implimentation that I was trying to create when I opened this bug is no longer needed, and I am unable to remember exactly what breaks.
It is most likely that it works fine with current jQuery UI. Can you close this ticket?
comment:7 Changed 10 years ago by
| Resolution: | → notabug |
|---|---|
| Status: | new → closed |
This bug was not fixed by the fix for ticket 4088, and I discovered it after 4088 was fixed.