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 25725 - getUserMedia constraints should be non-nullable
Summary: getUserMedia constraints should be non-nullable
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: Media Capture and Streams (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-15 12:26 UTC by Kiran
Modified: 2014-07-02 16:32 UTC (History)
2 users (show)

See Also:

Attachments

Description Kiran 2014-05-15 12:26:23 UTC 
In spec getUserMedia constraints is allowed to set Nullable [1].

but in step 4, The process is invoking errorCallBack with NotSupportedError, if requestedMediaTypes are empty.

It seems, requestedMediaTypes of constraints is mandatory to process getUserMedia.

I propose to indicate constraints attribute of getUserMedia to be non-nullable. 


[1] http://dev.w3.org/2011/webrtc/editor/getusermedia.html#dom-navigator-getusermedia
Comment 1 Harald Alvestrand 2014-06-30 13:54:19 UTC 
This seems simple, and is consistent with present code.

Note that not allowing Null doesn't allow us to remove the language about empty reuestedMediaTypes, because the user can pass {} as a parameter.

Assigning for editing.
Comment 2 Adam Bergkvist 2014-07-02 16:32:08 UTC 
Proposed (light) patch: https://github.com/fluffy/webrtc-w3c/commit/6da20fcbd689bd33e3132c52261c52fcff464f00