Assistance causes unintended attraction and wrong drops during drag

What it is

Unintended drag snapping occurs when an assistance system pulls a moving object toward a non-intended alignment line, grid, or container, leading to a wrong drop, incorrect alignment, or difficult escape. Minor selection tolerance becomes amplified in drag because object position continuously affects path and outcome.

Why it happens

Drag snapping commonly computes candidates from object edges, centres, or drop targets. As an object moves, geometric relations change; one snap can push it into another candidate's range or separate release position from raw hand position. Weak cues, high escape thresholds, or immediate commitment leave no time to detect and correct.

Studying it

Vary snap radius, release rules, and candidate feedback across alignment lines, grids, adjacent containers, and dense nodes. Measure wrong drops, cancellation, repeated drags, candidate switching, and undo. Observe paths, not only final location, to locate where assistance changed intent.

Where it stops holding

Snap can markedly reduce errors in regular tables, layout grids, and clear ordering slots. The issue arises in free placement, dense candidates, cross-container moves, or deliberately nonregular positions. Larger objects and lower zoom magnify differences between visual boundary and algorithm reference point.

Applying it

• Show snapped object, alignment line, and drop preview during drag, with easy escape before release.
• Offer temporary snap disablement or reduced strength on free canvases and fine positioning.
• Map undo, re-drag, and wrong-drop locations to revise rules that repeatedly capture the wrong candidate.

Related

• Same group: C1.14.1 Assistance changes actual hit boundaries and miscalibrates the user's position model · C1.14.3 Assistance must behave predictably rather than randomly
• Nearby: C1.08 Drag and drop · C1.12 Target snapping and sticky targets
• Search terms: drag snapping · wrong drop · pointing assistance