This is related to https://github.com/RubaXa/Sortable/issues/837
I feel people have been doing work around and hacks, but we really need the ability to stop sortable to complete its dom manipulation after drop/move/sort and allow developers to manually change the collection bound to the view in the onSort etc handlers.
i do it on the start event and it works fine for me...
onStart: function (/**Event*/evt) {
if(cancel_condition){
return false;
}
Return false on the onStart event is supposed to cancel the event...? Because it doesn't... I would love an answer to damianof question.
@arquadrado for me it does. Makes sense, it is done on the onStart to evaluate conditions.
The return false trick in onStart does not work for me neither unfortunately
See how it is implemented in any of the packages: https://github.com/SortableJS/
Ex.: https://github.com/SortableJS/angular-legacy-sortablejs/blob/master/angular-legacy-sortable.js#L162-L185
Most helpful comment
Return false on the onStart event is supposed to cancel the event...? Because it doesn't... I would love an answer to damianof question.