- From: François Beaufort via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Aug 2020 09:54:28 +0000
- To: public-webrtc-logs@w3.org
> > In the second query, if there are no cameras with PTZ capabilities, the PTZ request will be ignored and it will be treated like a regular camera request.
>
> It seems you say that, if there is no PTZ camera, the permission request will be { name: "camera", panTiltZoom: false }.
> Where is this algorithm defined?
It's not and it should be fixed in the spec. Thanks for raising this issue.
I've filed at https://github.com/w3c/mediacapture-image/issues/246
> Now, let's take the case of a setup with a PTZ camera but user persistently denied PTZ permission. getUserMedia({ video: { advanced: [{ pan: true }] } }) will trigger a permission request of { name: "camera", panTiltZoom: true }. The result of the permission request will be 'denied' since PTZ permission is denied. getUserMedia will then always reject.
> I might me misunderstanding things. In any case, more precisely defining the algorithms will help potential implementer understanding.
With `getUserMedia({ video: { advanced: [{ pan: true }] } })`, it will not reject as we're using advanced constraints here (optional then). It will be "downgraded" to a regular camera request.
However with `getUserMedia({ video: { pan: true } })`, the promise will always reject if user persistently denied PTZ permission.
--
GitHub Notification of comment by beaufortfrancois
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/243#issuecomment-675382685 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 August 2020 09:54:29 UTC