@dnd-kit/modifiers

Patch Changes

• Updated dependencies [00ec286, 995dc23, f629ec6, 99643f6, 6bbe39b, 545a41c, bcaf7c4]:
  • @dnd-kit/core@6.2.0

Patch Changes

• Updated dependencies [bc588c7, b417f0f, f342d5e]:
  • @dnd-kit/core@6.1.0
  • @dnd-kit/utilities@3.2.2

Patch Changes

• #823 b065c37 Thanks @DaniGuardiola! - Add missing peer dependency to @dnd-kit/modifiers

• Updated dependencies [da7c60d]:

  • @dnd-kit/core@6.0.6
  • @dnd-kit/utilities@3.2.1

Patch Changes

• Updated dependencies [4173087, 59ca82b, 7161f70, a52fba1, 40707ce, a41e5b8, bf30718, a41e5b8, a41e5b8, 035021a, 77e3d44, 5811986, e302bd4, 188a450, 59ca82b, 750d726, 5f3c700, 035021a, e6e242c, 035021a, 33e6dd2, 10f6836, c1b3b5a, 035021a]:
  • @dnd-kit/core@6.0.0
  • @dnd-kit/utilities@3.2.0

Minor Changes

• #567 cd3adf3 Thanks @clauderic! - Update modifiers to use draggingNodeRect instead of activeNodeRect. Modifiers should be based on the rect of the node being dragged, whether it is the draggable node or drag overlay node.

• #518 6310227 Thanks @clauderic! - Major internal refactor of measuring and collision detection.

  Summary of changes

  Previously, all collision detection algorithms were relative to the top and left points of the document. While this approach worked in most situations, it broke down in a number of different use-cases, such as fixed position droppable containers and trying to drag between containers that had different scroll positions.

  This new approach changes the frame of comparison to be relative to the viewport. This is a major breaking change, and will need to be released under a new major version bump.

  Breaking changes:

  • By default, @dnd-kit now ignores only the transforms applied to the draggable / droppable node itself, but considers all the transforms applied to its ancestors. This should provide the right balance of flexibility for most consumers.
    • Transforms applied to the droppable and draggable nodes are ignored by default, because the recommended approach for moving items on the screen is to use the transform property, which can interfere with the calculation of collisions.
    • Consumers can choose an alternate approach that does consider transforms for specific use-cases if needed by configuring the measuring prop of <DndContext>. Refer to the <Switch> example.
  • Reduced the number of concepts related to measuring from ViewRect, LayoutRect to just a single concept of ClientRect.
    • The ClientRect interface no longer holds the offsetTop and offsetLeft properties. For most use-cases, you can replace offsetTop with top and offsetLeft with left.
    • Replaced the following exports from the @dnd-kit/core package with getClientRect:
      • getBoundingClientRect
      • getViewRect
      • getLayoutRect
      • getViewportLayoutRect
  • Removed translatedRect from the SensorContext interface. Replace usage with collisionRect.
  • Removed activeNodeClientRect on the DndContext interface. Replace with activeNodeRect.

Patch Changes

• Updated dependencies [f3ad20d, 02edd26, c6c67cb, 6310227, e7ac3d4, 528c67e, 02edd26]:
  • @dnd-kit/core@5.0.0
  • @dnd-kit/utilities@3.1.0

Minor Changes

• #334 13be602 Thanks @trentmwillis! - Add snapCenterToCursor modifier

Patch Changes

• #437 0e628bc Thanks @chestozo! - Added PointerEvent support to the getEventCoordinates method. This fixes testing the PointerSensor with Cypress (#436)

• Updated dependencies [13be602, aede2cc, 05d6a78, a32a4c5, f96cb5d, dea715c, dbc9601, 46ec5e4, 7006464, 0e628bc, c447880, 2ba6dfe, 8d70540, 13be602, 422d083, c4b21b4, 5a41340, a13dbb6, e2ee0dc, 1fe9b5c, 1fe9b5c, 1f5ca27]:

  • @dnd-kit/core@4.0.0
  • @dnd-kit/utilities@3.0.0