Summary
@patternfly/react-topology now supports an optional ghost node (non-interactive placeholder) at a node's original position while the real node is being dragged, so edges do not appear to hang in empty space. This work should be reflected in the PatternFly design kit (Figma) so designers can spec and review the interaction consistently with implementation.
Upstream references
Design kit scope (suggested)
-
Add Figma representation(s) for the ghost / placeholder node state used during drag (visual treatment aligned with DefaultNode and existing topology tokens).
-
Document when the ghost appears vs. the live dragged node (interaction note or kit annotation), matching the optional API behavior in code.
-
If applicable, update topology examples or pattern frames so drag scenarios show the ghost for handoff and QA.
Acceptance criteria
Notes
Upstream also notes a related change in DefaultEdge around freezeEdgeDuringNodeDrag (see PR #311). Confirm whether kit edge documentation or examples need a small alignment pass.
Jira Issue: PF-3924
Summary
@patternfly/react-topologynow supports an optional ghost node (non-interactive placeholder) at a node's original position while the real node is being dragged, so edges do not appear to hang in empty space. This work should be reflected in the PatternFly design kit (Figma) so designers can spec and review the interaction consistently with implementation.Upstream references
Feature request: patternfly/react-topology#305 — Nodes - Add optional ghost node at original position during drag operations
Implementation (merged): patternfly/react-topology#311 — feat: show ghost node during node drag (includes design-review asset in the PR description)
Shipped on prerelease: comment on #305 — 6.5.0-prerelease.5
Design kit scope (suggested)
Add Figma representation(s) for the ghost / placeholder node state used during drag (visual treatment aligned with
DefaultNodeand existing topology tokens).Document when the ghost appears vs. the live dragged node (interaction note or kit annotation), matching the optional API behavior in code.
If applicable, update topology examples or pattern frames so drag scenarios show the ghost for handoff and QA.
Acceptance criteria
Ghost-node visuals and usage are documented in the kit in line with the merged react-topology behavior.
Any new styles use existing design tokens / library styles where possible.
Cross-link or changelog note pointing designers to the react-topology release when this lands in a stable channel (if kit ships before/after stable).
Notes
Upstream also notes a related change in
DefaultEdgearoundfreezeEdgeDuringNodeDrag(see PR #311). Confirm whether kit edge documentation or examples need a small alignment pass.Jira Issue: PF-3924