Re: Proposal + request for feedback: navigator.enumUserMedia

I would encourage you to look at the latest settings proposal [1],
which includes the ability to enumerate devices.  This would allow
applications to learn about devices over time and to select devices
that suit their application.

The settings API does not provide additional information about these
devices other than indicating existence.  The guidance that the task
force has so far receive indicates that increasing the fingerprinting
surface area of the browser is undesirable.  Any increase in
fingerprinting surface needs to be strongly justified.

[1] https://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/proposals/SettingsAPI_proposal_v6.html

On 6 February 2013 11:21, Rui Lopes <ruilopes@google.com> wrote:
> Hi everyone,
>
> I the course of playing around with navigator.getUserMedia, I bumped into
> some limitations both on the spec and its implementation in browsers.
> TL;DR: I wanted to see what stands in the way to create a DAW (Digital Audio
> Workstation) in the browser.
>
> While I started with audio, this problem can be further generalized to video
> as well. Here's a bunch of use cases that are difficult/impossible with
> navigator.getUserMedia as it stands:
>
> 1) Populating a dropdown list with available audio inputs;
> 2) Switching between front and back cameras on a mobile phone;
> 3) Programmatically select a specific media source.
>
> I've drafted an initial/incomplete spec + example usage, which can be read
> at https://github.com/ruidlopes/enumUserMedia
>
> Feedback & contributions are welcome!
>
>
> Cheers,
> Rui

Received on Wednesday, 6 February 2013 18:47:16 UTC