W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2014

Re: [whatwg] Media sink device selection on <audio>/<video>

From: Ami Fischman <fischman@chromium.org>
Date: Mon, 13 Jan 2014 14:51:03 -0800
Message-ID: <CAHuR8a9Gd-qWkJBHsE8SGT7O9_R-BYnhaUetUgS2Bi6LhEjpVw@mail.gmail.com>
To: Philip J├Ągenstedt <philipj@opera.com>
Cc: WHATWG <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
On Sun, Jan 12, 2014 at 8:47 PM, Philip J├Ągenstedt <philipj@opera.com>wrote:
[...]

> Do you mean to make this per-origin as well? (It will require storing
> that information per-origin forever, or until some invisible timeout.)
> That seems about as restrictive as one could make it, but is the API
> going to actually be useful in this state?
>

Sure, why not?
Canonical use-case: webrtc-using video-chat webapp allows the user to
select between speakers, wired headset, or bluetooth headset for its audio
output; the webapp already has gUM permission so now it can use
getMediaDevices() to enumerate output sinks and use the proposal here to
route the remote audio feed to the desired device.

Cheers,
-a
Received on Monday, 13 January 2014 22:51:28 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:15 UTC