[Mind] Design keyboard navigation for abstract nodes and referenced branches

Open
#1,155 0 comments 0 reactions 0 assignees View on GitHub

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

area: mind design enhancement

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-reference navigation 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from worktile/plait

All issues in worktile/plait

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.