[Mind] Design keyboard navigation for abstract nodes and referenced branches
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reading #1147 and the visible-node and layout-direction concepts it introduced. Work through examples for standard, directional, indented, and nested layouts, including collapsed and overlapping references. Done means the abstract-reference rules, selection priority, return behavior, and implementation tests are agreed before coding.
Written by the indexing model from the issue text.
Description
Context
#1147 adds arrow-key navigation for mind-map nodes and intentionally leaves AbstractNode behavior for a follow-up. Abstract nodes are different from normal tree nodes: they reference a range of sibling nodes instead of owning those nodes through a regular parent-child relationship. That makes navigation into, out of, and around an abstract node ambiguous.
Goal
Define a predictable keyboard-navigation model for an abstract node and the nodes or branches it references. The design should work across standard, directional, indented, and nested layouts without forcing abstract references into the normal parent-child model.
Suggested direction
- Decide whether an abstract node is always a selectable navigation target or only participates in particular directions.
- Represent the relationship explicitly, for example as an
abstract-referencenavigation relation, instead of treating referenced nodes as children. - Keep layout-relation navigation responsible for structural/reference semantics and use geometry navigation only as a fallback for visual proximity.
- Reuse the visible-node and layout-direction concepts introduced by #1147 where they fit, while keeping AbstractNode-specific rules isolated.
- Preserve navigation history when moving from an abstract node into its referenced range, if returning to the previously visited node feels natural.
Open questions
- Which referenced node should be selected when navigating from an abstract node: the first node, the nearest rendered node, or the previously visited node?
- In which direction should a referenced node navigate back to the abstract node?
- Should descendants of referenced nodes participate directly, or should navigation enter through the referenced top-level node first?
- How should collapsed or partially hidden referenced branches behave?
- How should overlapping abstract ranges and nested layouts affect candidate priority?
The interaction details can be refined through examples and tests before implementation.
- Dominant language
- TypeScript
- Stars
- 703
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from worktile/plait
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
area: tooling tracking
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
area: table design enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
area: text bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
documentation tracking
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
milind-soni/OpenMausBot#6730 ·
Maintainers usually reply within 1 day
-
`@angular/[email protected]` depends on vulnerable Vite 7.3.7 - GHSA-p4f5-76q4-ffq7 (Critical RCE)Openarea: @angular/build
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
angular/angular-cli#34764 ·
Maintainers usually reply within 1 day
-
status/need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-gemini/gemini-cli#30384 · 1 comment ·
Maintainers usually reply within 1 day
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:image documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day