Fence pointer capture ownership across node and edge gestures

This commit is contained in:
2026-11-09 18:35:43 +08:00
parent 2f385433be
commit 0813b8df53
8 changed files with 71 additions and 35 deletions
+14
View File
@@ -394,3 +394,17 @@ application registers frame settings and node style toolbars through an optional
DOM context, including portalled content; legacy and pre-engine renderers use no
registry. Other overlays need explicit registration. Current retention still
suspends culling for the view; it does not selectively mount each overlay target.
Pointer transport helpers (`ownsPointerCapture`, `acquirePointerCapture`,
`releasePointerCapture`) keep DOM capture separate from editor gesture ownership.
Move/up/cancel must match the active pointer ID. Lost capture also matches its
capture target and cannot cancel a target that already owns a newer platform
capture. Capture acquisition failure cancels the acquired edit lease; detached
release is idempotent. Node transforms and edge controls now share these checks
and cancel/release on blur or unmount. Native React Flow drag handling remains an
adapter path; these helpers do not replace the full tool/input controller system.
While a control owns an active capture, foreign pointer events reaching that
control are consumed without changing the lease; they do not fall through into
pane navigation/connection handlers. Outside an active control, unclaimed input
continues normally. Node drag cancellation only addresses its own pointer/token.