Skip to main content

Search and Top Navigation

#4875 closed bug (wontfix)

Opened September 24, 2009 09:03AM UTC

Closed November 03, 2012 05:49PM UTC

Sortable: fails if li element has overflow set to auto

Reported by: haydenchambers Owned by:
Priority: minor Milestone: 2.0.0
Component: ui.sortable Version: 1.7.2
Keywords: firefox, sortable, overflow Cc:
Blocked by: Blocking:

to reproduce in firefox 3.5

the key is the overflow:auto of the li

(without overflow its a visual disaster because of the floating content)

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

<html lang="en">
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
	<script src=""></script>
	<script type="text/javascript">
	<script type="text/javascript">
		$(document).ready(function() {
	<style type="text/css">
		ul { width:300px;padding:10px;border:1px solid black; }
		li { border:1px solid red;overflow:auto; }
		li span { float:left; }
		.tool { float:right; }
		<li><span>list item 1</span><span class="tool">x</span></li>
		<li><span>list item 2</span><span class="tool">x</span></li>
		<li><span>list item 3</span><span class="tool">x</span></li>
		<li><span>list item 4</span><span class="tool">x</span></li>
		<li><span>list item 5</span><span class="tool">x</span></li>

sort: function() { console.log("sorting"); }

reveals two calls before the li 'sticks' to the the mouse and further logs fail

Attachments (0)
Change History (3)

Changed November 17, 2009 06:37PM UTC by jzaefferer comment:1

milestone: TBD1.8

Changed October 11, 2012 02:54PM UTC by scottgonzalez comment:2


Changed November 03, 2012 05:49PM UTC by petersendidit comment:3

resolution: → wontfix
status: newclosed
summary: sortable fails if li element has overflow set to autoSortable: fails if li element has overflow set to auto

Thanks for taking the time to contribute to the jQuery UI project! I was able to recreate this problem in Firefox 3.6 with this: But it looks like the bug is not reproducible in Firefox 4.0+.

If you have a fix fore the problem in Firefox 3.5 feel free to submit a pull request on github.