- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Aug 2020 20:38:45 +0000
- To: public-webrtc-logs@w3.org
I fear we may have hit the limits of normative prose in field descriptions, and may need to modify algorithms. So for clarity, here's what I think we need: * At the start of [getUserMedia](https://w3c.github.io/mediacapture-main/getusermedia.html#dom-mediadevices-getusermedia)'s in parallel steps, add something like: 1. If the user has no PTZ cameras attached, remove all `pan`, `tilt`, and `zoom` members from `constraints.video` (this'll be reflected in `track.getConstraints()` on success only). * _**Note:** This removes a site's ability to use `OverconstrainedError` on `pan`, `tilt`, or `zoom`_ to detect PTZ abilities without risking a prompt if no PTZ devices exist. 2. (Move the [ptz-specific permission request modification](https://w3c.github.io/mediacapture-image/#pan) steps here (or further down where gUM requests permission). This order should clarify that: * PTZ constraints are completely ignored unless the user has at least one PTZ camera attached. * Sites cannot get `OverconstrainedError` on ptz constraints unless the user has a ptz camera attached. * Users can't be prompted for PTZ permission ("use & move") unless they have a ptz camera attached. * PTZ constraints still work in `track.applyConstraints` where they may trigger a PTZ permission prompt. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/246#issuecomment-684025628 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 August 2020 20:38:47 UTC