- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Aug 2018 14:39:56 +0000
- To: public-media-capture-logs@w3.org
A possible interpretation would be that getUserMedia({video: {echoCancellation: {exact: false}}}) should reject because no video candidate can provide an echoCancellation of false, though fitness distance is positive infinity.
However, it can be argued that a video track definitely has no echoCancellation, so maybe echoCancellation exact false should be accepted.
I think we should update the spec to explicitly say that properties not intended for the track type can be ignored, which would be in line with what browsers currently do.
--
GitHub Notification of comment by guidou
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/533#issuecomment-417343702 using your GitHub account
Received on Thursday, 30 August 2018 14:39:57 UTC