Opened 9 years ago
#9852 new bug
Wrong update event order on sortable connected lists
Reported by: | sebastien-p | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | none |
Component: | ui.sortable | Version: | 1.10.4 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
As you can see in this jsFiddle http://jsfiddle.net/bdatK/, dropping sortable items in a connected list fires those events in this exact order:
- update (source list)
- remove (source list)
- receive (destination list)
- update (destination list)
I think, to be consistent, this should be:
- remove (source list)
- update (source list)
- receive (destination list)
- update (destination list)
Or (not sure of this one):
- remove (source list)
- receive (destination list)
- update (source list)
- update (destination list)
Note: See
TracTickets for help on using
tickets.