Repair outgoing allocation drag boundary placement and feedback

2026-09-24 22:47:30 -07:00
parent 715036e132
commit 1a669130fb
12 changed files with 1047 additions and 16 deletions
@@ -2128,7 +2128,19 @@ performer change with diagram placement. The preview MUST identify the
 destination and preserve readable work and destination identity. Destination
 identity is shown outside the canvas, independently of explanatory or refusal
 text. The outlined target's hit region remains fixed throughout the gesture;
-feedback MUST NOT obscure the work or change its pointer-relative placement.
+feedback MUST NOT obscure the work. Preserve pointer-relative placement when
+the requested position is valid. When an outgoing drop would leave work
+overlapping its former performer, the editor MAY propose a minimal grid-aligned
+translation through a crossed performer boundary, with one grid unit of
+clearance. It MUST preview that exact position, translate the complete affected
+work group rigidly, and recheck all semantic and collision constraints on release.
+It MUST NOT move unrelated placements or search arbitrary free space. If no
+proposal is valid, a pointer-following outline MAY accompany the last valid
+preview; that retained preview MUST NOT authorize a refused release.
+Outgoing work headers MAY be partly outside the viewport provided each retains
+at least a 24-by-24 logical-pixel grab region. Releasing the pointer outside the
+viewport still cancels. Other assignment and Arrange gestures retain their
+complete-header visibility requirement.
 A clean click selects without applying unrelated drafts. A refused work press
 with an unapplied property draft MUST preserve its text, caret and focused
 editor. An accepted drag is one atomic model/source/history transaction: