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 17287 - PeerConnectionErrorCallback argument
Summary: PeerConnectionErrorCallback argument
Status: RESOLVED FIXED
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Web RTC Working Group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-01 20:46 UTC by Justin Uberti
Modified: 2014-10-31 15:51 UTC (History)
3 users (show)

See Also:

Attachments

Description Justin Uberti 2012-06-01 20:46:45 UTC 
As mentioned in the TODO, we need to decide if this should work like the getUserMedia error callback, which provides an object that holds the error information, or as speced here, where it just provides a string.

4.1.4 PeerConnectionErrorCallback

callback PeerConnectionErrorCallback = void (DOMString errorInformation)
          
DOMString errorInformation
Information about what went wrong. Open Issue: How does this work? Is it human readable? I18N? ENUM?

TODO: Open Issue: should this be defined as event like NavigatorUserMediaErrorCallback in getusermedia
Comment 1 Cullen Jennings 2012-10-24 19:17:40 UTC 
Can Anant help resolve this in his w3c preso ?
Comment 2 Harald Alvestrand 2014-10-31 15:51:26 UTC 
The spec currently says that it's an ERROR of type DOMError.