W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2012

[Bug 17287] New: PeerConnectionErrorCallback argument

From: <bugzilla@jessica.w3.org>
Date: Fri, 01 Jun 2012 20:46:45 +0000
To: public-webrtc@w3.org
Message-ID: <bug-17287-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17287

           Summary: PeerConnectionErrorCallback argument
           Product: WebRTC Working Group
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebRTC API
        AssignedTo: public-webrtc@w3.org
        ReportedBy: juberti@google.com
                CC: public-webrtc@w3.org


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

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Friday, 1 June 2012 20:46:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:28 UTC