Intent to Prototype: SelectAudioOutput API

188 views
Skip to first unread message

Chromestatus

unread,
Oct 11, 2024, 7:35:16 AMOct 11
to blin...@chromium.org, agp...@google.com, gui...@google.com

Contact emails

agp...@google.com, gui...@google.com

Explainer

None

Specification

https://w3c.github.io/mediacapture-output/#dom-mediadevices-selectaudiooutput

Summary

This API prompts the user to select a specific audio output device. This API allows the user to select an audio output device device per-origin when they have multiple devices available without giving access to "microphone" permissions. Instead "speaker-selection" permissions should be allowed for the use of this API. This chosen device can then be used by the setSinkId API for audio output. Currently, this can be done by using getUserMedia() API but that needs microphone permissions to allow the selection. This fails to work when there are no microphones and only audio output devices.



Blink component

Blink>WebRTC>Audio

Motivation

None



Initial public proposal

None

Search tags

selectAudioOutput

TAG review

None

TAG review status

Not applicable

Risks



Interoperability and Compatibility

None



Gecko: Shipped/Shipping

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None



Debuggability

None



Is this feature fully tested by web-platform-tests?

Yes

https://wpt.fyi/results/audio-output



Flag name on chrome://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/372214870

Launch bug

https://launch.corp.google.com/launch/4347445

Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5164535504437248?gate=5143981865041920

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages