This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23933 - Proposal: Change constraints to use WebIDL dictionaries
Summary: Proposal: Change constraints to use WebIDL dictionaries
Status: RESOLVED WONTFIX
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-27 13:12 UTC by Stefan Hakansson LK
Modified: 2014-01-07 10:32 UTC (History)
2 users (show)

See Also:

Attachments

Description Stefan Hakansson LK 2013-11-27 13:12:49 UTC 
The core of this proposal, which is outlined in [1] as "A. Don't violate WebIDL", is to use WebIDL dictionaries instead of the prose currently used for Constraints. The effect (apart from making speccing simpler) is that unknown mandatory constraints will succeed. To allow the app to control a way to probe the UA for which constraints it knows is added.

This bug is filed to make it simpler to record any decision we make related to this proposal.

[1] http://lists.w3.org/Archives/Public/public-media-capture/2013Nov/0161.html
Comment 1 Gili 2013-11-27 18:37:45 UTC 
Just to be clear: the implication of this proposal is that users will need to ask for a set of constraints, but then they will have to check that the returned device meets those constraints (because some of them may have been omitted as "unknown").

In summary: the specified constraints are no longer "mandatory", they are "mandatory if known".
Comment 2 Stefan Hakansson LK 2013-11-28 07:51:52 UTC 
(In reply to Gili from comment #1)
> Just to be clear: the implication of this proposal is that users will need
> to ask for a set of constraints, but then they will have to check that the
> returned device meets those constraints (because some of them may have been
> omitted as "unknown").

That is not true really. Since the proposal also includes a method that allows the app to probe for what constraints that the UA understands, it can first check, and if one or more constraints the app wants to use as mandatory are not known by the UA the app can at that stage decide to not go ahead and call gUM.
Comment 3 Stefan Hakansson LK 2014-01-07 10:32:18 UTC 
The discussion related to this bug clearly shows that people want to keep the current behavior (unknown mandatory constraints results in the error callback). This can not be done by using WebIDL dictionaries (at least not currently), so I'm closing this bug as "WONTFIX".

Stefan