[whatwg] Media sink device selection on <audio>/<video>
philipj at opera.com
Mon Jan 13 17:39:06 PST 2014
Perhaps :) I'm not on that list, but am fine leaving this to people
who have stronger opinions than me on the issue.
On Tue, Jan 14, 2014 at 6:36 AM, Ami Fischman <fischman at chromium.org> wrote:
> Hmm; I wasn't thinking in terms of per-device, only per-origin and
> Seems like a conversation for public-media-capture?
> On Mon, Jan 13, 2014 at 3:30 PM, Philip Jägenstedt <philipj at opera.com>
>> On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman <fischman at chromium.org>
>> > On Sun, Jan 12, 2014 at 8:47 PM, Philip Jägenstedt <philipj at 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.
>> OK, so a site that has been given access to any device using
>> getUserMedia can then enumerate all devices using getMediaDevices? I
>> interpreted "devices to which the user has already granted access
>> through getUserMedia" in the most restrictive (per-origin, per-device)
>> way possible...
More information about the whatwg