#149 new
Cyrus Collier

Sortable buggy when passed element w/ no id

Reported by Cyrus Collier | December 31st, 2008 @ 03:45 AM

When calling Sortable.create, one can of course pass either a DOM element or an element id name to the method since the method wraps the parameter with $(). However, at other points in the Sortable object, it assumes that the sortable element has an id, so when an element is passed with no id, the functionality becomes quite buggy. Dragging performance is choppy, dropping becomes inaccurate, and IE throws multiple errors for undefined objects. Problem is solved when calling Element.identify on the element prior to passing it to Sortable.create, but this simple check should be done within the Sortable object itself.

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