The app ignores Reduce Motion, and sidebar rows show Notes only on hover
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- swift
- Domain
- accessibility, frontend
Research direction
Start in Sources/SwitchboardApp/InboxView.swift:113, IssuesView.swift:169, and ContentView.swift:742 to inspect the three scroll animations, then read ContentView.swift:240 and the shared session row context menu at :246. Check how the app reads Reduce Motion and how the row menu is built. Done means all three scrolls respect Reduce Motion and Notes is available in the row menu; the issue asks for a VoiceOver pass after #398 and #392 land.
Written by the indexing model from the issue text.
Description
The app ignores Reduce Motion, and the sidebar row's Notes button appears only on hover, with no menu equivalent.
What happens
- The views don't read
accessibilityReduceMotion. The three scroll animations (InboxView.swift:113, IssuesView.swift:169, and ContentView.swift:742) always animate. - A sidebar row shows its Notes button on hover (ContentView.swift:240). Its context menu (:246) has Clean Up and Delete but not Notes. Open PR #375 rebuilds the row menus and doesn't add Notes either.
Why it matters
Reduce Motion users expect scrolling to jump instead of animate. A control that appears only on hover is hard to reach for keyboard and VoiceOver users unless it's also in a menu.
Suggested fix
- Wrap the three
withAnimationcalls in a Reduce Motion check. - Add Notes to the shared session row menu.
- Run a VoiceOver pass once the sidebar search field (#398) and the three-column layout (#392) land.
This is finding 15 of the #295 UI once-over.
- 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