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

Re: [mediacapture-main] Should we allow empty string device IDs? (#551)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 18 Jan 2019 22:42:46 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-455711741-1547851365-sysbot+gh@w3.org>
> it does not bring any value since it is not hiding anything.

The value added is it fits within the existing spec; we've not added to the cognitive load of the model exposed to users, which trumps implementation difficulties in the [priority of constintuencies](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies).

> 'default'/empty string also convey in a better way the intent, 

FWIW Chrome only supports this special "default" deviceId for microphones, not cameras, and Firefox recently removed this feature altogether, so I don't think we're keen on adding it back.

Currently in the spec, there's no expectation that users look at deviceIds to infer any special meaning. If they do then it's not web compatible.

> That said, enumerateDevices should not even be used to check for camera/microphone existence in Safari since non default devices are not exposed.

If users have to check they're on Safari, then we've failed. Presumably sites are already using this API to check for existence, as that works on most browsers today, and is an implicit guarantee in the model exposed in this spec. It seems late to change this.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/551#issuecomment-455711741 using your GitHub account
Received on Friday, 18 January 2019 22:42:47 UTC

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