From the “Review of Web Audio Processing: Use Cases and Requirements”
Need a requirement that audio controls not affect system audio settings i.e., should have impact just for audio under control of the Web application. For instance, it would be highly problematic if a "mute" in
the Web application muted all system audio. If other requirements mean system audio will be controllable from Web applications (this is not clear to me one way or the other right now), then instead the requirement is that users have an easy way to control whether to allow system audio settings to be impacted by in-application changes (e.g., via a user preference option in user agent).
This seems like a WONTFIX for me.
On the one hand, a web audio processing/synthesis API does only has in its scope the processing of whatever sources and destinations it is given, not beyond.
On the other hand there could be cases where the web application *is* the operating system, and such a requirement would be counterproductive.
This was echoed by Doug
in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0854.html :
> This one is more challenging. In a traditional browser, there is no way
> for the API to do that anyway, so there's no need to spell out the
> requirement. In a "system OS" browser (something like Boot2Gecko), there
> may not be any distinction between the browser and the OS, so this
> requirement proposal doesn't make sense there either.
No objection since July. Closing.