Opened 13 years ago
Closed 10 years ago
#4872 closed bug (notabug)
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.
Change History (5)
comment:1 Changed 13 years ago by
| Milestone: | TBD → 1.8 |
|---|
comment:3 Changed 11 years ago by
It does not look like there has been any activity on this as the issue is still occurring.
comment:4 Changed 10 years ago by
| Milestone: | 1.9.0 → 2.0.0 |
|---|
comment:5 Changed 10 years ago by
| 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.
Note: See
TracTickets for help on using
tickets.
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.