Cancel inherited drag velocity on release

Fixkamo-internal
Shipped
April 29, 2026 at 11:10 PM UTC
Author
kamo
Commit
b399696

The drag handler updates the head's motion value with rapid mx.set(nx) calls, which framer-motion uses to compute velocity. When the release path triggered a soft-push (because the dropped position grazed an edge or overlapped a tool window), the corrective spring inherited the drag's high velocity and overshot wildly — heads would "shoot across the page" and land elsewhere, sometimes off-screen. A stationary release worked because velocity decayed to zero first. Pass velocity: 0 in animateAnchorTo so every anchor placement starts from a clean velocity state. Also reset velocity for a follower's initial flight into a cluster (where the head being added may have just been a dragged anchor with momentum).

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing