Search and Top Navigation
#3178 closed bug (wontfix)
Opened August 13, 2008 02:36AM UTC
Closed August 27, 2008 02:19PM UTC
Last modified May 09, 2011 04:45PM UTC
Sortable update callback fires twice if connectWith is on
| Reported by: | anonymous | Owned by: | paul |
|---|---|---|---|
| Priority: | major | Milestone: | 1.7 |
| Component: | ui.sortable | Version: | 1.5.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
The update is fired for both of the containers, the old one and the new one. I'd tend to think most people would only want one update, fired for the container the sortable has been moved to.
if (ui.element[0] === ui.item.parent()[0]) {
// is when we want the callback to happen.
}
Attachments (0)
Change History (3)
Changed August 13, 2008 02:38AM UTC by comment:1
Changed August 27, 2008 02:19PM UTC by comment:2
| resolution: | → wontfix |
|---|---|
| status: | new → closed |
That is not a bug. I if you only want one callback, you can use the "receive" callback.
Changed May 09, 2011 04:45PM UTC by comment:3
This is too a bug. I have two lists that are sortable and they are connnected. I need to be able to handle the intra-list changes as well as the inter-list changes. I would only expect to see update fired once.
I meant to be logged in when I filed this. Oops.