https://bugs.kde.org/show_bug.cgi?id=375943
--- Comment #54 from pallaswept <[email protected]> --- (In reply to Dragan from comment #53) > It's not a jab at KDE team, it's simply frustrating that a feature that used > to work is no longer there. Sure is. > Did anyone manage to figure out what did Firefox and Chrome change, > seemingly at the same time? They both changed from the old way of generating sound, where each window had it's own sound handling (so, the process ID that was playing the sound, and the process ID of the window showing that tab, were the same ID, so KDE could match them up), to a central sound process that handles the audio for all the tabs and windows. This was part of an overall change to how webpages are handled, where each page is running in it's own separate process, sandboxed from the others for security. I had to ask a search engine for the dates, but I'm pretty sure this is correct: That was enabled by default in firefox 49 (e10s) in September of 2016 and Chrome 76 (Audio Service) in July 2019. Basically it happened ~roughly~ around the same time because there was a general industry push for better security in webpages. What's really frustrating is that on windows, both browsers send the necessary metadata to the sound service, to identify which process ID is associated with a sound stream (ie, which window is making that sound). They just don't do it on linux. For history, you can read about where they added metadata handling to firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=965653 Basically, it just never occurred to anyone there, that we'd want to identify the window playing the sound. The audio engine which firefox uses, cubeb, also does not have any facility to receive such metadata. They only have a field for the audio stream name (usually the tab title). So, we'd have to get firefox AND cubeb patched. As I mentioned before, they're infamously bad at this, even for critical and simple things like setting the volume. To be really frank, when it takes more than 5 years to merge a single line patch to fix every single linux user's volume control, it really feels like they just don't care at all. I sincerely hope a cubeb dev arrives here, merges that patch, and tells me I am wrong and an idiot. We should give up hope of this being fixed until a lot more people migrate from windows and complain to the browsers about this. When the browsers start to care a bit more about audio on linux, we might see some improvement. I'm just trying to direct the frustration that we are all feeling in this thread, to a productive place. -- You are receiving this mail because: You are watching all bug changes.
