- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Oct 2020 10:25:58 +0000
- To: public-webrtc-logs@w3.org
> I don't like non-ortohonal constraints either, but I don't think you get around the "non-orthogonality" by making it a second, separate step. Agreed that constraints are the only way for device picking. There is a tension though between constraints and the in-chome device picker we envision in the future. It would be good to understand what we think of the future of constraints in that in-chome device picker world. Back to my original point, I think that the current API makes it very hard for web developers to handle correctly non-orthogonal constraints. Your proposal here further strengthens the idea that we should expose native preset information to web developers. This could be through getCapabilities or in some other form. Once web developers have that information, applyConstraints is probably fine as long as we ensure that there will be an easy and unambiguous way for web developers to end up selecting the particular preset. I guess this could be dealt with as a separate issue -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/739#issuecomment-714396077 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 October 2020 10:26:00 UTC