#4872 closed bug (notabug)

Opened September 22, 2009 02:26PM UTC

Closed November 04, 2012 07:12PM UTC

Sortable update callback fires twice if connectWith is on

Reported by: mikespokefire Owned by:
Priority: major Milestone: 2.0.0
Component: ui.sortable Version: 1.7.2
Keywords: Cc:
Blocked by: Blocking:
Description

The "update" callback is fired twice, even if you drop the item into the same container.

In ticket #3178 you say to use the "receive" callback, unfortunately this cannot be used as the sortable item that you are moving hasn't changed containers, so therefore it never fires the "receive" callback.

Attachments (0)
Change History (5)

Changed November 18, 2009 10:16AM UTC by jzaefferer comment:1

milestone: TBD → 1.8

Changed March 04, 2011 04:39AM UTC by j0nscalet comment:2

_comment0: Anyone made any progress with this bug? I just ran into it and it seems to have gotten overlooked (changed 16 months ago). Granted this is my first time finding and comment on a UI bug but I just wanted to check up. \ Thanks. → 1299213593676940

Anyone made any progress with this bug? I just ran into it and it seems to have gotten overlooked (changed 16 months ago). Granted this is my first time finding and commenting on a UI bug but I just wanted to check up.

Thanks.

Changed August 12, 2011 03:48AM UTC by sops21 comment:3

It does not look like there has been any activity on this as the issue is still occurring.

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

milestone: 1.9.0 → 2.0.0

Changed November 04, 2012 07:12PM UTC by mikesherov comment:5

resolution: → notabug
status: new → closed

Thanks for contributing, but this STILL the correct behavior as pointed in #3178. Both events have distinct targets to distinguish between the two lists that got updated.