Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#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 5 years ago by Scott González

  • Resolution set to fixed
  • Status changed from new to closed

Sortable: Fixed destroy to remove instance from element. Fixes #8094 - .sortable() after destroy does not work.

Changeset: 4259978d39c6c9d8ce292ad0839d0d42c45400f0

comment:2 Changed 5 years ago by Scott González

Sortable: Fixed destroy method to call parent destroy method. Fixes #8094 - .sortable() after destroy does not work.

Changeset: 988b803be3085111cb8d741b99ab09151dc7f1b5

comment:3 Changed 5 years ago by scottgonzalez

  • Milestone changed from 1.9 to 1.8.18
Note: See TracTickets for help on using tickets.