Branch and Board status text is set in faint tertiary gray
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- swift
- Domain
- accessibility, frontend
Research direction
Read the cited lines in Sources/SwitchboardApp/SessionView.swift and Sources/SwitchboardApp/ContentView.swift, then check the related changes in PRs #375, #260, #382, and #383 for file overlap. The requested change is to use .secondary for the branch and folder line and the Board status line; done when both use the stronger text color and the project builds.
Written by the indexing model from the issue text.
Description
Two pieces of text a user reads to decide are set in .tertiary, which is too faint to read comfortably on a light background.
What happens
- SessionView.swift:246-252: the session header's branch and folder line.
- ContentView.swift:1145-1146: a Board card's status line, such as "In review 12m · stopped", which says how long the card has waited.
A 1024 pt capture of main shows both as pale gray. #355 already moved the Inbox detail's branch to .secondary.
Why it matters
.tertiary on a white background is well under the 4.5:1 contrast that WCAG asks for body text. macOS uses tertiary for decoration and placeholders, not for information.
Suggested fix
Use .secondary for both, and keep .tertiary for decoration.
This is finding 13 of the #295 UI once-over. Open PRs #375 and #260 change SessionView.swift, and #382 and #383 change the Board in ContentView.swift.
- Dominant language
- Swift
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 308
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 haacked/switchboard
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
haacked/switchboard#420 ·
Maintainers usually reply within 1 day
-
priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
haacked/switchboard#403 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
haacked/switchboard#395 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
haacked/switchboard#391 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
haacked/switchboard#419 ·
Maintainers usually reply within 1 day
All issues in haacked/switchboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Enzoo404/gravitybox#21 ·
Maintainers usually reply within 1 day
-
area: sidebar enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ZigaoWang/zigzag#351 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
manaflow-ai/cmux#46584 ·
Maintainers usually reply within 1 day
-
android:core ios:core
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day