With FF mobile on Android I still had ongoing sound after closing
FF completely (at least as far as I know) and I had to reboot my phone.
It's quite concerning that websites are able to do this. While
it is the browsers fault to support all that javascript crap I
think this is also a bug in Android.
> It's quite concerning that websites are able to do this.
They've been able to do this for a long time and for valid reasons (think of a PWA audio player, like a podcast app).
Unfortunately this used to get abused very often. I remember seeing bugs in ads that would: stop your Spotify playback (due to how audio apis work on phones), and continue playing in background (again, this is a feature, but often abused). iOS is much better in that regard, with stricter autoplay policies, etc...
What's super concerning is that audio worked even when the page was closed. Once I kill the tab, the entire process should be killed too.
So yeah, it's possible that it's just an FF bug purely because being able to play audio in BG is a valid feature BUT there should be no audio when the tab has been killed. My guess is that from the OS perspective, the tab is still running.
My another guess is that it has something to do with some clever techniques regarding reducing the app size.
It's quite concerning that websites are able to do this. While it is the browsers fault to support all that javascript crap I think this is also a bug in Android.