https://bugs.kde.org/show_bug.cgi?id=375943
--- Comment #52 from pallaswept <[email protected]> --- (In reply to Dragan from comment #51) > Full 9 years later and this regression is still not resolved. Let me explain what's taking so long. We want to have the mute button appear only on "the window that's making the sound" that button would mute. "The window that's making the sound", is a thing that does not exist. The sound is not coming from any of the windows of your browser. *All* of the sound from the browser is coming from *one* process that the browser spawns, that just plays sound. When a tab in a window wants to play a sound, the tab asks that sound process to play it. The tab in the window doesn't play sound. The sound process *just* makes sound, and doesn't even have a window. So, to solve this, we need some magic that tells us what sound comes from what window. The sound server (pulse, pipewire) can be given a way to identify the window, by the browser. If the browser does this, KDE can make the UI work like you want. Browsers do not do this, so KDE can not make the UI work like you want. In firefox, that process sets the title of the tab that's playing the sound, but still does not tell us which window has that tab. We could maybe find that window from the tab title though, so there is some hope, but it would be hard to code and require an extension. In Chromium, that process sets nothing and there is no data for us to know which tab in which window is playing which sound. There is no possibility that it can ever work like you want on chromium, until they fix this. So KDE can't fix this. Firefox and Chromium need to fix this. I understand that it's frustrating for you, and I am trying to help you to get it fixed. It can't happen here, KDE can not do it. Chromium must fix it. Firefox could improve things, too. But really, this whole thing is blocked by chromium. BTW, firefox has had broken volume control on linux for 15 years and they have the extremely simple 1 line patch to solve it for 5 years and still haven't merged it. Browsers aren't fast to fix things, even if you do it for them. Expect this to never work like we wish it did. I'm sorry to be the bearer of bad news. But if you do want to fight for it, fight in a chromium bug report. All we can do here is wait until someone does that. -- You are receiving this mail because: You are watching all bug changes.
