Post
There's actually an open Chromium issue about this: issues.chromium.org/issues/45041... issues.chromium.org/issues/41346... Which is where I started. It mentions updating the pulse stream information after creating the stream.
So now I have a 600 line patch for Chromium, but I have absolutely now experience in contributing to Chromium and since it's LLM-generated code, I don't have C++ experience, it doesn't have any tests, and only benefits Linux+Pulseaudio, it's quite unlikely that it ends up in Chrome.
0 reposts0 likes