- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Apr 2020 17:43:35 +0000
- To: public-webrtc-logs@w3.org
So the idea is to be able to force a PTZ capability while keeping the property unconstrained.
The second option is a lot more consistent with the constraintable pattern, although I wouldn't call it ptzPermission, but just ptz to indicate that you want the PTZ capability. What you want is the capability to do PTZ, not necessarily to prompt for permission, since different browsers have different permission models.
I would personally prefer the second model, although the first one can work too if the value true is more explicitly defined to mean that you are requesting the PTZ capability while leaving specific numeric values unconstrained. Do not define it as {} since that one also normally means unconstrained, even if in this case we want to interpret {} as requesting the PTZ capability too.
For numeric constraints {}, null, or not saying anything, are all equivalent and it normally means unconstrained.
--
GitHub Notification of comment by guidou
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/225#issuecomment-620755764 using your GitHub account
Received on Tuesday, 28 April 2020 17:43:37 UTC