#101 new
Stephan H. Wissel

Sortable on <ol> doesn't renumber in IE

Reported by Stephan H. Wissel | October 11th, 2008 @ 05:37 AM | in 1.8.3 bugfix release

I have the following html snippet:


<ol id="test">
<li>Alpha</li>
<li>Beta</li>
<li>Gamma</li>
<li>Delta</li>
<li>Epsilon<li>
</ol>

and the following code in a script lib:


Sortable.create("test");

Works as expected in FF. In IE (tested on IE6 and IE7) the numbers of the ordered list are not renumbered but each row dragged is reset to #1.

Looks like a bug to me. Is there are workaround until fixed?

Comments and changes to this ticket

  • ronin-15560 (at lighthouseapp)

    ronin-15560 (at lighthouseapp) November 20th, 2008 @ 07:42 PM

    • Milestone set to 1.8.3 bugfix release

    This is an IE bug, and I do not know of a workaround. I'll try to look into it for 1.8.3 but can't promise anything. If anyone has a patch for this, please go ahead and post it here.

  • Kevin Miller

    Kevin Miller February 11th, 2009 @ 04:23 AM

    I found a workaround. If you add the style="display:list-item;" to the

    • item, IE 7 will renumber the dragged item in the context of the larger list.

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.

Source available from github
The Git repository resides at:
http://github.com/madrobby/scriptaculous

Check out the current development trunk with:
git clone git://github.com/madrobby/scriptaculous.git

As script.aculo.us 1.xx is feature-frozen, this development trunk is for bugfixes only.

New development should happen only for
script.aculo.us 2.

Creating a bug report
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, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket

Pages