[FR]: Have each tab be listed with its website title in audio sources in KDE Plasma Audio Devices dropdown
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
The issue does not name files, tests, or implementation entry points. Start by tracing how Helium exposes media-playing tabs to KDE Plasma's Audio Devices dropdown and compare that with how Firefox supplies per-tab titles. Done means each media source is listed using its website title rather than repeating “Helium”; confirm this in the Plasma dropdown with multiple media-playing tabs.
Written by the indexing model from the issue text.
Description
Description
I'd like to request a feature where each media-playing tab in Helium will have a bespoke title (taken from website title) in the dropdown list of audio sources in KDE Plasma Audio Devices menu.
Who's implementing?
- I'm willing to implement this feature myself
The problem
When you click on Plasma Audio Devices dropdown (in the Plasma panel), with e.g. Firefox you get bespoke names for each tab based on website titles (e.g. [YouTube Video title], [title of a news website where a video is playing], [Twitch stream title], etc). With Helium, if you e.g. have five media-playing tabs open, you just get "Helium" listed five times in that dropdown. This makes lowering/increasing volume for a specific video/audio source tedious, as you have to manipulate volumes for each "Helium" listing until you stumble upon the correct listing.
Possible solutions
Have the browser send a bespoke listing from each media-playing tab to the Audio Devices dropdown.
Additional context
OS: PikaOS 4 x86_64
DE: KDE Plasma 6.5.4
WM: KWin (Wayland)
Browser: Helium Version 0.14.5.1 (Official Build, Chromium 150.0.7871.114) deb (64-bit)
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days