Nav-panel folder label truncates at the maximum text scale
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- accessibility, frontend
Research direction
Start by locating the nav-panel folder and host label layout, then find the smoke layout assertions and existing clipping checks; the issue does not name their files. Run the smoke checks and add a case for --text-scale: 1.5 at 1280x800. Done means the specified folder name is fully visible, the host is visible or its truncation is intentional with a tooltip, and no horizontal scrolling or affordance clipping is introduced.
Written by the indexing model from the issue text.
Description
Goal
Keep the nav-panel folder label readable at the maximum UI text scale instead of ellipsising it.
Priority
p3. It only appears at --text-scale: 1.5 and nothing is lost or hidden behind the ellipsis — the row is still clickable and the folder can be identified from its expanded children — but it is a visible layout defect in an accessibility feature.
Current gap
At --text-scale: 1.5 in a 1280x800 window, the folder label "Core network" gets a 98px box and needs 125px at 19.5px, so it ellipsises. The 1.15 preset is fine. Found while running row M-28 of the manual matrix.
Recorded in PR #96 (docs/testing/manual-matrix.md §Findings, F-3) and deliberately not fixed there, because that change is documentation only.
Scope
Give the folder label room at large text scales: let the row grow vertically, allow the label to wrap, or widen the panel at the top of the scale. Whatever is chosen must not reintroduce horizontal scrolling in the nav panel or clip the expand/collapse affordance.
Acceptance criteria
- At
--text-scale: 1.5in a 1280x800 window, a folder name of at least 12 characters is fully visible in the nav panel, with no ellipsis. - The same holds for a host name of at least 24 characters, or the truncation is documented as intentional with the tooltip that reveals the full value.
- The nav panel does not scroll horizontally at any supported text scale.
- The smoke layout assertions still pass, including the existing clipping checks, and a case covers the maximum text scale.
- The fix uses layout only; no raw px font sizes or colours are introduced in component CSS.
Boundaries
Do not redesign the nav panel or reduce the available text scale. This is not the place to revisit host-row density.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 68
Getting set up
- No Dockerfile or Docker Compose file
- No 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 bonzo81/comnd
-
p3 testing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
maintenance p3 testing
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement p3
Difficulty 4/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
appandflow/stim#5258 ·
Maintainers usually reply within 1 day
-
area/docs framework/hugo help wanted language/markdown
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 68/100
lingdojo/kana-dojo#33660 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
drizzle-team/drizzle-orm#6639 ·
Maintainers usually reply within 4 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100