Optional audio visualizer for tabs
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
Research direction
Start by reading the tab views and Settings → Tabs implementation to locate how audible state, pinned tabs, and Split View are represented. Then check the project’s audio and Reduce Motion handling on Chromium and WebKit. Done means an off-by-default setting with Fill, Bars, and Wave previews applies consistently to all tabs, respects Reduce Motion, and leaves mute and close controls intact; the issue proposes tests and a recording.
Written by the indexing model from the issue text.
Description
The problem
When audio starts playing in a background tab, I end up scanning the tab list for the speaker icon. I’d like to be able to spot the tab at a glance.
What you'd like
I like how Crest puts a small audio visualizer along the bottom of the tab that’s playing sound. I’d like to add something similar to Yab as an option in Settings → Tabs, off by default.
I’d keep the settings simple: one switch and three styles with previews: Fill, Bars, and Wave. The same choice would apply to tabs in the sidebar and across the top, including pins and tabs in Split View. The existing mute and close controls would stay as they are.
In Chromium, it would react to the tab’s actual audio. In WebKit, it would just animate while the tab is audible. With Reduce Motion on, it would stay still.
I’ve attached a mockup showing what it looks like on and off. If this fits Yab, I’d be happy to build it myself and send a PR with tests and a short recording.
Related: #17 is about Arc’s music notes on pinned tabs; #134 is about the mini player. This proposal is for the tabs themselves.
How you manage today (optional)
No response
Yab version (optional)
No response
- Dominant language
- Swift
- Stars
- 648
- Forks
- 56
- Avg merge
- 21h 14m
- Merged PRs (30d)
- 22
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 yetanotherbrowser/yab
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yetanotherbrowser/yab#1008 ·
Maintainers usually reply within 2 days
-
area: passwords Broken bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yetanotherbrowser/yab#923 ·
Maintainers usually reply within 2 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#918 · 1 reaction ·
Maintainers usually reply within 2 days
-
iPhone: the + button and the checkmark sit on top of the Space switcher in the bottom barPossibly taken @ChaseRoofener claimed this 3 days ago. OpenAnnoying area: iphone bug needs info
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yetanotherbrowser/yab#915 · 3 comments ·
Maintainers usually reply within 2 days
-
CONTRIBUTING.md and CI run scripts/runs/tests_for.py, which is not in the repositoryPossibly taken @serafimcloud claimed this 2 days ago. OpenAnnoying in progress
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
yetanotherbrowser/yab#875 · 1 comment ·
Maintainers usually reply within 2 days
All issues in yetanotherbrowser/yab
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Ranchero-Software/NetNewsWire#5572 ·
Maintainers usually reply within 11 days
-
api beginner story
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NCSU-App-Development-Club/ios_fall_26#86 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
swift-server/async-http-client#950 · 1 comment ·