Re: [mediacapture-main] Clarify behavior of using wrong-type constraints

`deviceId` is a cross-domain constraint. `TypeError` would still work,
 unless we were to introduce a new constraint in one domain first, and
 later change our minds and add it to another domain. In that case 
`TypeError` would bite us on backwards compatibility.

Given how Chrome and Edge already work, I could live with:

-     unknown - ignore
-     wrong-domain exact constraints - disregard all sources 
(OverconstrainedError)
-     wrong-domain ideal constraints - ignore (i.e. skip when 
calculating fitness distance)

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

Received on Wednesday, 12 October 2016 14:53:59 UTC