W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2019

Re: [mediacapture-main] What constraint name should be exposed in case of a getUserMedia query with multiple failing constraints (#562)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 25 Jan 2019 15:43:50 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-457615207-1548431029-sysbot+gh@w3.org>
> this requires to process all constraints

As does success. We're happy to implement this FWIW, and don't anticipate difficulty, as optimizing a failure path is of low value to us.

Compared to what's already missing for WPT, I think this change pales. If anything, it decreases implementation variance, simplifying tests.

Most importantly, I believe this PR is something editors can merge now without controversy.

> I would prefer the spec to allow returning an empty constraint name (in pre-grant case at least)

I think that's going to be harder to get through at this point (this spec is in CR). *OverconstrainedError* and the whole constraints language was designed for the pre-grant case. If you think we can get rid of it, I would personally support it, but also bet against it succeeding (have you seen [section 7.2](https://w3c.github.io/mediacapture-main/getusermedia.html#overconstrainederror-object)? someone must really want it) 😉

In any case, I don't see this PR as an obstacle to that, so in the interest of progress, I vote we merge it, and open a new issue for that.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/562#issuecomment-457615207 using your GitHub account
Received on Friday, 25 January 2019 15:43:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:10 UTC