- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Mar 2017 14:35:06 +0000
- To: public-media-capture-logs@w3.org
> @miguelao don't touch applyConstraints in Chrome without talking to @guidou
This issue does not relate to Chrome implementation but to the Spec wording, but thanks for the advice... ? 🤔 . @guidou let me know if you don't feel in the loop after having reviewed 7 patches of mine related to Constrainable Pattern in the last 7 days :smile:
Although I understand the point that
> it's WebIDL dogma that applyConstraints({}) and applyConstraints() should mean exactly the same thing.
this issue is about what is supposed to happen when `applyConstraints({})` or `applyConstraints()` is called, which is not stated anywhere in the Spec (also my concern that `encode function behaviour in the semantics of the arguments` is valid).
At least some editorial comment stating what is supposed to happen when `applyConstraints()` is called with no arguments is needed.
--
GitHub Notification of comment by miguelao
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/438#issuecomment-288418040 using your GitHub account
Received on Wednesday, 22 March 2017 14:35:12 UTC