v0.3.1

   🐞 Bug Fixes

• Fixes issue #110, adds focus and blur event handlers on node to toggle draggable as needed for firefox  -  by @sashamilenkovic in #110 (17ad9)
• Only calls preventDefault on parent container for certain keydown actions if the currentTarget is its equivalent  -  by @sashamilenkovic (3eeef)
• Fixes issue withe firefox draggable attribute when draggable items themselves are focusable  -  by @sashamilenkovic (e980a)

    View changes on GitHub

v0.3.0

   ⚡️Performance improvements

• Previously, to handle styling of a synthetically (non-natively) dragged node, a clone of the dragged node was created and appended to the document body. To ensure consistent styling, a recursive copy of the computed styles of the original dragged element was performed, including its children, and those styles were then assigned to the clone. However, with DOM elements that had many children, this proved to sometimes cause performance issues. Other drag and drop libraries do not append to the document body, but instead to the parent of the original dragged node. This however runs into an issue where moving the dragged element between overflow containers will not work (the dragged element will not be shown). The implementation @formkit/drag-and-drop now uses is to append the dragged element to its parent container, but then utilize the Popover API to lift the dragged element to the top layer and avoid those overflow issues.

• More work on synthetically scrolling elements with overflow when moving to the edges of the container.

    🐛 Bug fixes

• Fixes issue where touch-action: none was erroneously assigned to dragged elements.  -  by @sashamilenkovic in #127

• Fixes issue in FireFox where input selection was disabled for draggable items and their children  -  by @sashamilenkovic in #110

• Fixes general issues on Fire Fox mobile  -  by @sashamilenkovic in #109

• Fixes issue where duplicate aria-live regions were rendered  -  by @sashamilenkovic in #111

v0.2.6

   🐞 Bug Fixes

• Fixes issue where in certain cases handleNodeDrop and handleParentDrop are both called  -  by @sashamilenkovic (74433)

    View changes on GitHub

v0.2.5

   🐞 Bug Fixes

• Fixes issue where request animation frames during synth drag was not cancelled because it was referencing the global prop and not the state obj  -  by @sashamilenkovic (a1860)

    View changes on GitHub

v0.2.4

   🐞 Bug Fixes

• Fixes issue where dragstart would fire when pointerdown was held  -  by @sashamilenkovic (cc5ab)

    View changes on GitHub

v0.2.3

   🐞 Bug Fixes

• Fixes issues described in #105  -  by @sashamilenkovic in #105 (87701)

    View changes on GitHub

v0.2.2

   🐞 Bug Fixes

• Fixes issues brought up in #105  -  by @sashamilenkovic in #105 (bec69)

    View changes on GitHub

v0.2.1

   🐞 Bug Fixes

• Fixes issues #103 and #104  -  by @sashamilenkovic in #103 and #104 (cb35f)

    View changes on GitHub

v0.2.0

    🚨 Breaking Changes

• Multi-drag and selections plugin now removed and part of core functionality. To enable multi drag, set the multiDrag to true in the parent configuration.

• Swap plugin has been removed in favor of dropOrSwap plugin.

• Drag and drop class names for synthetic dragging (non native drag events) have been changed.

   💪 New Features

• Adds new insertion plugin https://drag-and-drop.formkit.com/#insert

• Adds new dropOrSwap plugin https://drag-and-drop.formkit.com/#drop-or-swap

• Adds new event listeners https://drag-and-drop.formkit.com/#events

   🐞 Bug Fixes and improvements

• Addresses issue #16. makes accessibility improvements to the core of @formkit/drag-and-drop.

• Addresses issues #62, #54 and #29 by introducing workaround to use non-native implementation by setting nativeDrag to false in parent configuration.

• Addresses issue #94. When picking up an element synthetically for dragging purposes, we clone the element and append it to the document body. In order to ensure that styles that were applied at its origiinal position within the dom are applied when it is moved up the document, we recurse over the computed styles and apply it to the cloned node. There is now a configuration property to skip the application of these computed styles deepCopyStyles .

• Addresses issue #77. Now uses pointer events to synthetically moved the dragged element as opposed to touch events.

• Addresses issue #46. Adds event handlers that can be configured at the global or parent level: https://drag-and-drop.formkit.com/events

• General improvements to synthetic scrolling

v0.1.5

   🐞 Bug Fixes

• Exports multidrag dragstart function, fixes types definitions in docs and config  -  by @sashamilenkovic (b597d)

    View changes on GitHub