Opened 5 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:

  1. update (source list)
  2. remove (source list)
  3. receive (destination list)
  4. update (destination list)

I think, to be consistent, this should be:

  1. remove (source list)
  2. update (source list)
  3. receive (destination list)
  4. update (destination list)

Or (not sure of this one):

  1. remove (source list)
  2. receive (destination list)
  3. update (source list)
  4. update (destination list)

Change History (0)

Note: See TracTickets for help on using tickets.