Strangely this is broken only in Firefox and Opera (IE, Chrome and Safari works as it should).
Any suggestions for a quick fix?
<html>
<head>
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js" type="text/javascript"></script>
<script src="http://ajax.googleapis.com/ajax/libs/jqueryui/1.8.2/jquery-ui.min.js" type="text/javascript"></script>
<script>
$(document).ready(function(){
$('#sortable').sortable();
});
</script>
</head>
<body>
<span id="sortable">
<p contenteditable="true">One apple</p>
<p>Two pears</p>
<p>Three oranges</p>
</span>
</body>
</html>
I had a similar issue, but it actually happened due to "disableSelection" call on an element.
I have found another "solution" to this problem.
When declaring your sortable, you should add a cancel: option like this:
This version does not force your cursor at the start, but you also can't drag using this field. I'd advice wrapping the
<p>
in a container which has some sort of dragging handle (like the dots at the start of every row in gmail).side remark:
':input,button'
is required, because that is the default option. If you do not add these, you get similar problems with inputfields and buttons.I had the same problem and it was because I was using the function
disableSelection()
togethersortable()
The Patrigan answer is correct, but there's a slightly better way to specify the cancel, such as:
Yes so for me it was the combination of adding:
and then taking off the
.disableSelection();
so i'm left with:
Actually this is working, as you can see by pressing tab: the editable element receives focus. I think the problem is that the sortable plug-in is hijacking the
mousedown
event and thus preventing the editable element from receiving focus when you click on it.A workaround is to add a
mousedown
event handler to the editable element that ensures it receives focus: