- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2016 23:40:41 +0000
- To: public-media-capture-logs@w3.org
@martinthomson That can't happen, because wrong-domain constraints are equally wrong for all sources in a domain. The fitness distance algorithm only makes sense for constraints in the valid domain, and infinity should clearly never enter into a distance calculation the way it is written. I think it's wrong to lump in "future constraints" (for which we have getSupportedConstraints() to detect) with wrong-domain constraints which really should be TypeError or completely ignored IMHO, because *video* will never support *volume*, and thus is always a pilot error. I think cross-domain constraints are a bad idea for the same reason. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/409#issuecomment-253078753 using your GitHub account
Received on Tuesday, 11 October 2016 23:40:48 UTC