Re: [mediacapture-main] What happens to constraints that are not applicable? Ignored or OverconstrainedError?

I think the spec would benefit from clarification in this area.
It is clear that properties that are not supported at all are ignored by WebIDL.
The spec does not explicitly mention what should happen with properties that are intended to be used by only one track type (e.g., echoCancellation).

The practical interpretation seems to be that properties not intended for a track type are ignored.
I tried getUserMedia({video: {echoCancellation: {exact: false}}}) in Chrome, Firefox and Edge, and all of them returned a stream with video track, with no echoCancellation setting.

>From an implementation perspective, I think this is the right thing to do. Otherwise, for every new property defined for only one track type, the code for all track types would need to be updated instead of only the code for the intended type.

-- 
GitHub Notification of comment by guidou
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/533#issuecomment-417341916 using your GitHub account

Received on Thursday, 30 August 2018 14:34:48 UTC