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

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

From: Philip Jägenstedt <philipj@opera.com>
Date: Tue, 14 Jan 2014 06:30:36 +0700
Message-ID: <CAMQvoC=Hbm2iwmGNA=LC8r7+UtR9xZKmz6WOAyDc0n-6_g3JNQ@mail.gmail.com>
To: Ami Fischman <fischman@chromium.org>
Cc: WHATWG <whatwg@whatwg.org>, Ian Hickson <ian@hixie.ch>
On Tue, Jan 14, 2014 at 5:51 AM, Ami Fischman <fischman@chromium.org> wrote:
> 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.

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...

Philip
Received on Monday, 13 January 2014 23:31:02 UTC

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