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 25788 - Spec should explicitly specify whether the return types can be nullable or not.
Summary: Spec should explicitly specify whether the return types can be nullable or not.
Status: RESOLVED WONTFIX
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: public-media-capture@w3.org
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-18 14:33 UTC by Kiran
Modified: 2014-09-23 06:53 UTC (History)
3 users (show)

See Also:


Attachments

Description Kiran 2014-05-18 14:33:34 UTC
The return types of certain function may be null in certain scenarios.
This has been specified for getTrackById 
"Return type: MediaStreamTrack, nullable", 
but missed to specify for other functions. This should be specified for all the possible cases

clone - should return null in case of any error occurred while processing.
and may be for other functions like
getCapabilities, getConstraints, getSettings etc.
Comment 1 Dominique Hazael-Massieux 2014-09-12 15:04:36 UTC
There are no error conditions defined for clone, getCapabilities, getConstraints, getSettings, and I'm not clear what kind of error might occur. 

Thus I don't think their return values should be nullable.
Comment 2 Stefan Hakansson LK 2014-09-23 06:53:15 UTC
There has been no evidence of the need for more cases where the return type can be null. Closing as "WONTFIX".