#6 new

Sortable list scrolling way past the end

Reported by rubyd | May 13th, 2008 @ 01:11 PM | in 1.8.3 bugfix release


I've encountered a problem with Sortable (see attached HTML file):

I've got a sortable UL inside a small DIV-container with style overflow:scroll. Only part of the sortable list is visible, scrolling with the UI controls works.

The Sortable object created for the list has option scroll: set.

Now, when grabbing an element from the top of the list and dragging it to the lower part of the visible portion, the list starts to scroll (as expected), but won't stop when its end has been reached (unexpected and undesirable).

Sorting without scrolling works fine.

Seen on:

  • Firefox 3.0b5 on Ubuntu
  • Firefox on Windows
  • IE7 on Windows
  • Prototype 1.6.0
  • script.aculo.us 1.8.1

To test the attached minimal example, put it in one dir with the prototype and script.aculo.us js-files.

Thanks and cheers


Comments and changes to this ticket

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