<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>25957</bug_id>
          
          <creation_ts>2014-06-03 10:03:39 +0000</creation_ts>
          <short_desc>PeerConnection should have an onerror event handler</short_desc>
          <delta_ts>2014-12-15 10:39:27 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebRTC Working Group</product>
          <component>WebRTC API</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>LATER</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Harald Alvestrand">harald</reporter>
          <assigned_to name="Justin Uberti">juberti</assigned_to>
          <cc>nohlmeier</cc>
    
    <cc>public-webrtc</cc>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>107189</commentid>
    <comment_count>0</comment_count>
    <who name="Harald Alvestrand">harald</who>
    <bug_when>2014-06-03 10:03:39 +0000</bug_when>
    <thetext>At the May 20 meeting of WEBRTC, it was agreed that errors on a PeerConnection that aren&apos;t associated with a specific object or function need to be reported through an &quot;error&quot; event on the PeerConnection itself.

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

This needs to be added to the WebRTC spec.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>108971</commentid>
    <comment_count>1</comment_count>
    <who name="Nils Ohlmeier">nohlmeier</who>
    <bug_when>2014-07-15 20:51:37 +0000</bug_when>
    <thetext>DTLS errors probably fall into this category as well.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>114381</commentid>
    <comment_count>2</comment_count>
    <who name="Harald Alvestrand">harald</who>
    <bug_when>2014-10-31 18:05:12 +0000</bug_when>
    <thetext>The TURN server authentication error may be covered by adding a DTLSTransport object.

Assigning to Justin.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>114382</commentid>
    <comment_count>3</comment_count>
    <who name="Justin Uberti">juberti</who>
    <bug_when>2014-10-31 18:06:28 +0000</bug_when>
    <thetext>Covered as part of onicecandidateerror (23920) and DtlsTransport.onstatechange</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>116313</commentid>
    <comment_count>4</comment_count>
    <who name="Dominique Hazael-Massieux">dom</who>
    <bug_when>2014-12-15 10:39:27 +0000</bug_when>
    <thetext>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.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>