W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2019

Re: [mediacapture-main] Is enumerateDevices list order significant? (#608)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Thu, 18 Jul 2019 20:55:02 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-512983910-1563483301-sysbot+gh@w3.org>
> Why is the default device necessarily the "best fit", unless the spec says so.

Yes, the spec does not talk about best fit.
The spec says that "User Agents are encouraged to default to using the user's primary or system default camera and/or microphone (when possible) to generate the media stream".
If the default camera/mic are first in the enumerateDevices list, everything seems more consistent.

> With respect to the first question, would formalizing that behavior bring something to the developer that otherwise was not already available?

Some web developers are interested in picking the default system device (at least the default microphone) and they have to use different approaches in Chrome, Firefox and Safari.
One straightforward way of helping developers which does not seem to require any change in browsers is to use the order in the list for this purpose.

If we expose this 'default device' information, the follow-up question is whether a devicechange event should be fired when the default device is changing, like when the user went to the system UI to change the default microphone.

Another related question for browsers exposing a 'default' microphone device is whether, while capture is ongoing with the default microphone and the user decides to change the system default microphone, the browser should change or not of actual microphone for the ongoing capture.
This question is probably outside the scope of the spec.

GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/608#issuecomment-512983910 using your GitHub account
Received on Thursday, 18 July 2019 20:55:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:25 UTC