The _closest() method already defined a way to do what _matches() was
trying to accomplish. This pulls the functionality out of _closest() so
that it can be reused outside of _closest() but refactors _closest() to
use this new _matches() method.
For instance, say you are sorting tbody's within a table element. There
can also exist tfoot and thead within the table element. The _index()
function assumes that the list of elements within the parent is
homogenus (ie: just li's below an ol/ul). This isnt the case when
sorting tbody under table. This is edge case until you want to group
tr's under a table and sort on those groupings.
when nesting Sortable's, we're not interested in this error:
"HierarchyRequestError: Failed to execute 'appendChild' on 'Node': The new child element contains the parent."
As done in the other place where `dataTransfer` is used.
This is to support fake html5 drag and drop events, where `dataTransfer` is not accessible. Use case: Selenium testing with ePages-de/chromedriver-html5-dragdrop
removed the default behaviour to append the cloned Element to the body.
now the cloned Element gets added in the same parent, with the addition
of the class defined in options.fallbackClass.
added the possibility to change the fallback class.
added the possibility to decide wheter the fallback should be cloned
into the same parent or to the document's body.
modified the private _onMove prototype, so it calls events on it's
source Element like it's sibling function _dispatchEvent
added the handleMove, which listens to the onMove events to the react
mixin
added forcePolyfill option.
forcePolyfill is made to make cross-browser testing more easy.
forcePolyfill provides a reliable, consistent cross-browser Solution for
Sortable.
forcePolyfill gives us the possibility to change the way "dragged items"
lok like.