Files
Netcatty/components/vault
LaiYueJi 3bf2242ac4 fix(vault): clear host drag state when the source node is unmounted
Dragging a host card in grid view left it stuck at opacity-45 until the
user started another drag on it.

The grid preview reorder runs from onDragOverCapture, so the dragged card
can move into a different virtual row while the drag is still active. In
VirtualizedHostCollection each row is a separate React parent, so crossing
a row boundary unmounts and remounts the card. The browser still dispatches
dragend at the original node, but a detached node no longer bubbles the
event up to the container's onDragEndCapture, so draggingHostId was never
cleared. A short drag that stayed inside one row kept the node mounted,
which is why dragging again appeared to fix it.

- bind a native dragend listener on the source node at dragstart; it is
  dispatched at that node and still fires after React unmounts it
- always reset drag state in onDropCapture: after a grid preview reorder
  the card under the cursor is the dragged card itself, so
  draggedHostId === targetHostId fell through every branch without
  resetting
- apply the same fix in useVaultItemReorder, which backs the keychain,
  port forwarding, proxy and known-hosts lists, and in SnippetsManager
2026-08-21 23:02:55 +08:00
..
2026-06-10 10:41:42 +08:00