- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Aug 2020 00:10:53 +0000
- To: public-webrtc-logs@w3.org
> Supporting this pattern adds some complexity to the specification and to implementations. If it is a bad pattern, why adding this complexity? On the contrary, I think special casing this is what would add complexity. Right now it's the same algorithm. Good or bad, I think it's important that behavior is predictable. I also don't think there's necessarily anything bad with setting pan, tilt and zoom immediately. That's an app choice, much like a car adjusting seat & steeringwheel when a driver gets in. > There is also the edge case of getUserMedia failing to applyConstraints while user granted device: the camera moved even though the web page never received a MediaStreamTrack. This seems slightly annoying. That would be an implemention bug I think, since applying constraints is [step 6.6](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-same-permission) in the `getUserMedia` algorithm, and is done [_"In a single operation"_](https://w3c.github.io/mediacapture-main/getusermedia.html#dfn-applyconstraints-algorithm) once there's nothing left that can fail. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-image/issues/229#issuecomment-682252926 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 00:10:55 UTC