« Changelog History


Sortable   v1.8.0 Release Notes

Release Date: 2019-01-15 // over 5 years ago
    • 💅 (#869, #592, #1358, #1119, #1378, etc): Dragover revamp, added options direction, swapThreshold, invertSwap, and invertedSwapThreshold. Read more. Resolved many of the issues where sorting is "not realistic". Grid-style sorting should work as well.
    • 💻 #1373: Autoscroll revamp, added option bubbleScroll, and better cross-browser compatibility
    • #1303: dragoverBubble for fallback
    • Bubbling of dragover event will only be stopped when element is inserted into a sortable if dragoverBubble=false
    • 👍 Automatic detection for pointer event support
    • #1389: Touch delay fix on mobile
    • #1382: Firefox event path fix
    • 🛠 Cloning fixes
    • 🛠 Pull/Put function fixes
    • #1352: Saving on both Sortables if dragged from one to another
      • get and set don't both need to be defined to work properly
    • #1276 : Native Drag and Drop ghost fix
    • Firefox: prevent selection when dragging
    • (#1409, #1323, #1095, #1204, #1087): Added onChange event
    • 🔄 Changed when dragstart and dragstarted are fired in fallback to match native HTML
    • Made pointer events mutually exclusive with mouse and touch events, to prevent duplicate event firing
    • #1151: Added easing option for animation easing
    • #1184: Click event no longer fired on drop when using fallback
    • 🛠 #1404: Fixed ghost element dimensions
    • (#1123, #1423): Ghost element is relative to containing block (prevents unwanted ghost element offset when using CSS translate)
    • #1301: Ghost element adheres to CSS scaling
    • 🚚 (#1093, #1236, #1054, #1214): Added removeCloneOnHide option
    • 👍 #1321: Much better support for nested sortables
    • #1305: Made it easier to add items to empty sortables with emptyInsertThreshold option
    • 0️⃣ #1416: Solidified pull/put behavior. Pull/Put are false by default when dealing with different groups, but true by default when dealing with the same group. They can be overridden in both cases.
    • #1079: The ghostClass that is applied is the target sortable's ghostClass, not that of the source sortable
    • 🛠 Many bug fixes