Re: [mediacapture-screen-share] Clarify that we only process/TypeError on applicable constraints (#95)

There's existing language (recently added) to say "ignore non-applicable constraints" in the selectSettings algorithm. Can what you are looking for be accomodated by broadening that language?
Though I'm worried that we may declare something that throws on {volume: {exact: 'wrong'}} (because it understands that exact volumes take numbers, not strings) non-compliant; I think that in Chrome we do the typechecking/conversion pass before we do the "is this constraint applicable" pass - which your suggestion would render non-conformant.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at using your GitHub account

Received on Friday, 21 December 2018 13:43:25 UTC