Mullvad Browser disable Web Audio API when disabling WebRTC?

This issue is for Mullvad Browser but I can't find it in the projects list through the anonymous ticket system.

https://mullvad.net/en/browser/hard-facts Differences with Tor Browser WebRTC is enabled Web Audio API is enabled (needed for WebRTC)

It would then follow that disabling WebRTC in the browser extension should also disable the Web Audio API.

Is this done?

I see that dom.webaudio.enabled is still true after disabling WebRTC. However I notice that this is true on Tor Browser as well so maybe this is the incorrect preference? Or maybe the hard facts documentation is out of date and Tor Browser now allows Web Audio API.

I would also like to put forward my suggestion that WebRTC be disabled by default and there be UI to allow the user to enable it when needed. Having read all the various WebRTC Firefox/Tor Browser/Mullvad issues, I have no confidence that there aren't implementation flaws that could result in leaks or fingerprinting. The Mozilla team has made so many mistakes along the way that it is almost laughable that a privacy browser is enabling it by default.