on arch here. haven't seen the problem yet, and I'm on 52.0. why am I not affected? I don't have pulseaudio installed (only some client libraries. lib32-libpulse, to be precise).
this doesn't look good. thanks for the post.
this doesn't look good. thanks for the post.
https://git.archlinux.org/svntogit/packages.git/tree/trunk/P...
line 97 for reference
guess I'll be using Chromium when that day comes, as I'd rather not run PulseAudio.
That’s what caused this, because Mozilla doesn’t have the manpower to rewrite two backends, and so had to choose one (with the pulse backend being preferred, as the pulse maintainers help mozilla and fix bugs on their side, while mozilla reports getting no assistance or anything from the ALSA maintainers).
Sad reality is that they are trying to not hire competent people while having features implemented well. Mozilla is vastly understaffed for the magnitude of the project.