Fix graph node activation
This commit is contained in:
parent
4c82e1643d
commit
8ac4fe2a67
13 changed files with 65 additions and 21 deletions
|
|
@ -1,12 +1,12 @@
|
|||
# Active slice
|
||||
|
||||
```text
|
||||
Slice: DFG-12 modal node inspection (complete)
|
||||
Goal: Let users inspect any visible graph node without losing their current neighborhood or viewport.
|
||||
In scope: A native modal dialog; full node metadata and content; mouse and keyboard activation; Escape, close-button, and backdrop dismissal; an explicit Explore neighborhood action; interaction-contract checks; JavaScript syntax validation; and complete regression verification.
|
||||
Out of scope: Graph mutation; source editing; persisted modal state; nested dialogs; arbitrary templates; external hosting; canonical writes; or any new HTTP endpoint.
|
||||
Done when: Activating a graph node opens an accessible inspection dialog, dismissing it preserves the current graph, explicit exploration loads the selected neighborhood, and the complete DocForge gate passes.
|
||||
Owners: DocForge owns dialog state and interaction. The configured project continues to own graph facts. The MCP process continues to own the validated snapshot and listener lifetime.
|
||||
Slice: DFG-13 graph activation reliability (complete)
|
||||
Goal: Make ordinary graph-node clicks reliably open the modal and remove obsolete empty-canvas guidance after a neighborhood renders.
|
||||
In scope: Defer SVG pointer capture until drag threshold crossing; preserve drag suppression; honor the empty-state hidden attribute; focused interaction-contract checks; JavaScript syntax validation; and complete regression verification.
|
||||
Out of scope: Graph mutation; source editing; alternate layouts; modal redesign; arbitrary templates; external hosting; canonical writes; listener lifecycle changes; or any new HTTP endpoint.
|
||||
Done when: Ordinary node clicks remain targeted at the node and open its modal, panning still captures and suppresses click only after a real drag, rendered graphs hide the empty-state instruction, and the complete DocForge gate passes.
|
||||
Owners: DocForge owns pointer and empty-state behavior. The configured project continues to own graph facts. The MCP process continues to own the validated snapshot and listener lifetime.
|
||||
```
|
||||
|
||||
**Next gate:** None planned. Measure actual graph-browser use before extending layout, export,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue