[FR]: Have each tab be listed with its website title in audio sources in KDE Plasma Audio Devices dropdown

Open
#346 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
linux, shell
Domain
desktop

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

feat
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.