FragiolaDnD
Documentation
More

Limitations and roadmap

What dnd does not do yet, the limits known today, and what comes next, from publishing the packages to adapters for other frameworks.

Roadmap

dnd's first set of capabilities is complete: draggable, droppable, sortable and swappable, each its own entry. What comes next:

  1. Publishing, once the maintainer has validated the library: the packages on npm, a changelog and these pages on fragiola.com.
  2. Other adapters: the core is framework-free so that Vue, Angular and others can follow React.

Not planned

  • Sorting: virtualised sortable lists, multi-select sorting, nested sortable trees and sorting across windows.
  • Motion: built-in drop animations. The shifts' transitions are your CSS (animating shifts).
  • Modifiers beyond auto-scroll (axis lock, snap to grid, restrict to a container), multi-select drags and drags across windows.

Shipped CSS, icons, text, a mandatory provider and HTML5 drag and drop as the move mechanism are out by design.

Known limits

  • The drag sources are larger than their targets. Over the shared entry, /draggable adds +5.0 KB min + gzip (target +2 KB), /sortable +7.9 KB (target +2.5 KB) and /swappable +5.8 KB (target +1.5 KB). They share one drag-source machinery, paid once: see bundle size.
  • The grid strategy suits items of one size. An item moved in a grid takes its new place's corner; items of varied sizes keep their order but may not line up. Lists (verticalList, horizontalList) take items of any size.
  • A group name is a droppable id during a sort. It shares its scope's droppable id space: keep group names and droppable ids distinct.
  • A drag never crosses documents. A drag inside a Dockable popout stays in that window, and a drag cannot carry an item from the main window into a popout.
  • Auto-scroll uses the scroll range measured when the drag starts. Content that grows during the drag (a list that loads more) is not scrolled into until the next drag.
  • An onMouseDown on a draggable does not run. The press is claimed on pointerdown, which suppresses the compatibility mouse events; use onPointerDown. click still fires.
  • Firefox scroll anchoring. In a scroll container, Firefox may take a dragged or shifted element as its scroll anchor, and scroll the container back by as much when the core clears its translate. The packages ship no CSS, so set overflow-anchor: none on the container yourself (the auto-scroll and sortable examples do).
  • Grid Layout integrations are local only until Grid Layout is on npm: see with Grid Layout.