Search and Top Navigation
#3019 closed bug (fixed)
Opened June 20, 2008 03:04PM UTC
Closed June 24, 2008 07:29PM UTC
Last modified June 26, 2008 07:08PM UTC
sortables bug with option 'stop'
| Reported by: | Vaskerville | Owned by: | paul |
|---|---|---|---|
| Priority: | major | Milestone: | 1.5.1 |
| Component: | ui.sortable | Version: | 1.5 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
One would think that the 'stop' option for Sortables would fire after sorting has completed AND the cloned helper class has deleted itself - so it is possible to return the list id's as they exist at completion.
For instance, if I have a list with id's...
<li id='i1'>1</li>
<li id='i2'>2</li>
<li id='i3'>3</li>
<li id='i4'>4</li>
And I drag 4 to position 2 I will get (reported via stop using a callback function to examine what's happening)...
<li id='i1'>1</li>
<li id='i4' style='visibility: hidden;'>4</li>
<li id='i2'>2</li>
<li id='i3'>3</li>
<li id='i4' class='ui-sortable-helper'>4</li>
And then, only when it has truly completed executing will I get...
<li id='i1'>1</li>
<li id='i4' style=''>4</li>
<li id='i2'>2</li>
<li id='i3'>3</li>
Thanks