#8094 closed bug (fixed)
.sortable() after "destroy" does not work
| Reported by: | zuckel | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.8.18 |
| Component: | ui.sortable | Version: | 1.8.17 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
In my scenario I need to activate and deactivate sortable lists a lot. After upgrading from 1.8.16 to 1.8.17 my sortables will only work the first time.
Example: <div id="sortStuff">
<div>text</div> <div>text</div> <div>text</div>
</div>
<script> $('#sortStuff').sortable(); $('#sortStuff').sortable("destroy"); $('#sortStuff').sortable(); </script>
Items will be sortable in 1.8.16, but not in 1.8.17.
Change History (3)
comment:1 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed 10 years ago by
Sortable: Fixed destroy method to call parent destroy method. Fixes #8094 - .sortable() after destroy does not work.
Changeset: 988b803be3085111cb8d741b99ab09151dc7f1b5
comment:3 Changed 10 years ago by
| Milestone: | 1.9 → 1.8.18 |
|---|
Note: See
TracTickets for help on using
tickets.
Sortable: Fixed destroy to remove instance from element. Fixes #8094 - .sortable() after destroy does not work.