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 25957 - PeerConnection should have an onerror event handler
Summary: PeerConnection should have an onerror event handler
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Justin Uberti
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-03 10:03 UTC by Harald Alvestrand
Modified: 2014-12-15 10:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Harald Alvestrand 2014-06-03 10:03:39 UTC 
At the May 20 meeting of WEBRTC, it was agreed that errors on a PeerConnection that aren't associated with a specific object or function need to be reported through an "error" event on the PeerConnection itself.

The exemplar event was a failure in TURN server authentication; another is the perennial "internal error".

This needs to be added to the WebRTC spec.
Comment 1 Nils Ohlmeier 2014-07-15 20:51:37 UTC 
DTLS errors probably fall into this category as well.
Comment 2 Harald Alvestrand 2014-10-31 18:05:12 UTC 
The TURN server authentication error may be covered by adding a DTLSTransport object.

Assigning to Justin.
Comment 3 Justin Uberti 2014-10-31 18:06:28 UTC 
Covered as part of onicecandidateerror (23920) and DtlsTransport.onstatechange
Comment 4 Dominique Hazael-Massieux 2014-12-15 10:39:27 UTC 
WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues

Please subscribe to the issues you want to keep watching.