Sortable Performance - Ticket #4410

Sortable Performance - Ticket #4410

This ticket was closed with the following comment:<div>
</div><div><span class="Apple-style-span" style="font-family: Arial, Helvetica, Verdana, sans-serif; font-size: 12px; ">"Patch isn't working, since this move from mouseCapture to mouseStart heavily destroys some functionality: If you add new elements to a sortable list, say via an ajax call, they're automatically valid draggables because of the check being there in mouseCapture already - if it wouldn't, they wouldn't be considered a target, and therefore the drag fails."</span></div>
<div><font class="Apple-style-span" face="Arial, Helvetica, Verdana, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 12px;">
</span></font></div><div><font class="Apple-style-span" face="Arial, Helvetica, Verdana, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 12px;">What are the chances that items are actually added to the sortable in the middle of a sort?  This really seems like an edge case to me, and certainly not something that needs to be natively supported if it causes performance issues.  Wouldn't an alternative solution to this be to call a refresh method on the sortable list if you modify the list in the middle of a sort?</span></font></div>