Use data on the ui.item to transport the original Sortable index for the update() function. This way extensions can set/access this info in their own custom Sortable functions. see #22696
git-svn-id: http://core.svn.wordpress.org/trunk@23067 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This commit is contained in:
parent
48382b4b0a
commit
98fb6e45d7
|
@ -3180,8 +3180,7 @@
|
|||
},
|
||||
|
||||
initSortable: function() {
|
||||
var collection = this.collection,
|
||||
from;
|
||||
var collection = this.collection;
|
||||
|
||||
if ( ! this.options.sortable || ! $.fn.sortable )
|
||||
return;
|
||||
|
@ -3200,13 +3199,13 @@
|
|||
|
||||
// Record the initial `index` of the dragged model.
|
||||
start: function( event, ui ) {
|
||||
from = ui.item.index();
|
||||
ui.item.data('sortableIndexStart', ui.item.index());
|
||||
},
|
||||
|
||||
// Update the model's index in the collection.
|
||||
// Do so silently, as the view is already accurate.
|
||||
update: function( event, ui ) {
|
||||
var model = collection.at( from ),
|
||||
var model = collection.at( ui.item.data('sortableIndexStart') ),
|
||||
comparator = collection.comparator;
|
||||
|
||||
// Temporarily disable the comparator to prevent `add`
|
||||
|
|
Loading…
Reference in New Issue