Sometimes evt.from is different from evt.item.parentNode because the item has been moved already so using evt.item.nextSibling won't work when doing evt.from.insertBefore, because nextSibling is not a child of evt.from.

So in those cases we use evt.clone.nextSibling instead.

Remove Polymer from bower dependencies

Fix to knockout sorting when dragging item index 1 to 0.

Allow a custom setState handler on the using component

The items would not swap positions when you dragged item with index 1 to
the top of the stack at index 0.

Add Polymer Support

Only components having a state are currently working correctly with the sortable mixing. The proposed fix is to allow custom state handling method to be passed in as config.

Delete log.txt

Should this file be in the repo?

more reliable way to get the DOM Node

with React v0.14 this.refs.*.getDOMNode() is deprecated,
we have to use this.refs.* instead, to reference the DOM Node.

this is a implementation, that is backward compatible

* misspelled ref in README fixed
* fixed Demo of forceFallback

Add `getContainer` option for better react version support

And so on: #558, #547, #542, #537, #532, #516, #500, #489, #489, #447, #475, #459, ##422, #411, #356

Bugfix in jquery.binding.js

Added Browserify support for ng-sortable

knockout-sortable Remove dom element reference to viemodel and use local variable instead

The var syntax is missing. Added to explicitly define local variable.

Use closure local variable instead of attaching the element to viewmodel. This is to prevent error caused by bound dom element as in issue 559.
https://github.com/RubaXa/Sortable/issues/559