- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Mar 2017 15:42:23 +0000
- To: public-media-capture-logs@w3.org
My interpretation of the current wording of the spec is that applyConstraints should update track and/or source settings to those that best match the new constraints, but without switching the source.
According to the spec, any supported set of settings is equally good at satisfying the empty constraint set, so doing nothing is a valid result for applyConstraints({}). Changing settings to any other supported value (e.g., default values, even random values) is equally spec compliant as long as it doesn't contradict constraints from other tracks.
--
GitHub Notification of comment by guidou
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/438#issuecomment-288440738 using your GitHub account
Received on Wednesday, 22 March 2017 15:42:29 UTC