#37 new
Ken Collins

Make inline this.destroy call for Sortable.create only focus on Sortable.sortables[element.id] and bypass Sortable._findRootElement called by this Sortable.destroy.

Reported by Ken Collins | July 4th, 2008 @ 08:21 PM

While developing the latest HomMarks I ran into an issue where sortables that contain sortables were being destroyed when I crated a new sortable member.

For instance, using my site as an example, the parent column sortable will be destroyed when I crate a box sortable for a new column added to the page via local JS DOM building. This is because Sortable.options will use _findRootElement which will recursively look upwards for sortables. This is good behavior as many other places rely on this... but when creating a new Sortable on the page with Sortable.create, it is best to focus only on calling the destroy action when the element ids match up.

No comments found

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket