Editor's Path Properties section has 'Convert Node Type' (corner / smooth / symmetric) but the symmetric/smooth distinction is unclear in the UI — user clicks 'smooth' and gets 'symmetric' (or vice versa) #359
Labels
No labels
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:verify-failed
bug
deferred
feature-request
in-progress
needs-decompose
needs-triage
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/Kimi_Agent_Brother_10_Digitizing_App#359
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finding
The Convert Node Type (per #191) has 3 options: corner, smooth, symmetric.
A user with a node:
The visual difference between smooth and symmetric is subtle when the handles are equal length. A user can't tell which they got.
The fix is clearer labeling or visual feedback.
Where
src/components/editor/EditorContextMenu.tsx(the Convert Node Type submenu)src/components/editor/EditorRightPanel.tsx(Node Properties section)Suggested fix shape
Help page link: a "Learn more" link to the Help page's "Node types" section.
Use cases:
Severity
Low. The user can experiment. New users notice the confusion.
Discovered by
Gap analysis (2026-10-02) of editor node type UI.
Related
feat(#359): clarify corner/smooth/symmetric Node Type buttons + visual previews
The Node Type tri-button in the editor right panel only showed the labels 'corner / smooth / symmetric' — a user picking 'smooth' to avoid a corner could land on the more-restrictive 'symmetric' with no way to tell the difference visually. #359 adds three affordances:
The fix lands on the right-panel surface (the context menu's Convert Node Type submenu already uses an inline tri-button group with active highlighting and adding tooltips there would conflict with hover navigation through the submenu — the educational content lives in the panel where the user is more likely to linger on the choice).
EditorRightPanel.tsx + new issue-359.test.tsx (6 tests, all pass). LSP clean, eslint clean, tsc -b clean. 20 pre-existing test failures (#329/#331/#333/#334 geometry error) are unchanged on main.
Commit:
07db222925