- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Sep 2020 18:45:03 +0000
- To: public-webrtc-logs@w3.org
> * enumerateDevices() needing to happen after getUserMedia() You can call enumerateDevices before getUserMedia. It will tell you whether there are microphones and/or cameras, which should give you enough to craft your UI and getUserMedia request. > * 'fake' data now, complete data later should be considered evil This is not fake data, this is limited data and complete data if user agrees. > * Tackle fingerprinting issues; no deviceIDs are ever seen by a page without user permission The current design enforces this. > * Prevent 99% of developers having to build device selection UIs unnecessarily: There is a proposal for a device picker that hopefully can address that. > whilst its clever to try and channel deviceID as just another constraint, the separation of 'what' media the client has access to, versus 'how' it samples that media, could be inevitible. I agree. getUserMedia model is made more complex than it should because we try to mix selection and setup in one step. Selection should be the primary focus of getUserMedia, setup can be mostly delegated to applyConstraints. To make progress here, it would be nice to understand the exact cases you find difficult or impossible to implement with the current API design. This would make it much easier to try updating the current design. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/719#issuecomment-685927435 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 September 2020 18:45:05 UTC