- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Aug 2020 07:09:10 +0000
- To: public-webrtc-logs@w3.org
> Good or bad, I think it's important that behavior is predictable.
Well, it is very predictable if the web page cannot express that behavior, except as part of applyConstraints :)
I could see User Agents wanting to reset PTZ to the initial position, for instance in case the PTZ position was previously set by another origin.
Also, navigator.mediaDevices.getUserMedia({ video : { width : 481 } }) is still not very interoperable between browsers.
navigator.mediaDevices.getUserMedia({video: { pan: 10, tilt: true }})) might follow the same path.
Things are a bit simpler with applyConstraints since it starts with a device initial state that is exposed to the web page.
The initial state of the camera in getUserMedia algorithm is somehow User Agent specific.
> [_"In a single operation"_](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-applyconstraints-algorithm)
step 6.6 is potentially calling the applyConstraints constraints twice for audio and video tracks, so "In a single operation" is not always guaranteed. step 6.6 is also handling the case of an error. If it is guaranteed to never happen, we should remove it from the spec.
--
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/229#issuecomment-682366991 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 August 2020 07:09:12 UTC