onerror in RTCRtpReceiver and RTCRtpSender objects #95
From: Anniruddh Koppal (Persistent Systems Ltd.) email@example.com
onerror eventhandler needs to be added to RTCRtpSender/RTCRtpReceiver objects.
The text was updated successfully, but these errors were encountered:
…cribed in Issue 57 w3c#57 - Added support for getRemoteCertificates(), as described in Issue 67 w3c#67 - Removed filterParameters and createParameters functions, as described in Issue 80 w3c#80 - Partially addressed capabilities issues, as described in Issue 84 w3c#84 Addressed WebIDL type issues described in Issue 88 w3c#88 - Addressed Overview section issues described in Issue 91 w3c#91 - Address readonly attribute issues described in Issue 92 w3c#92 - Added ICE restart method to address the issue described in Issue 93 w3c#93 - Added onerror eventhandler to sender and receiver objects as described in Issue 95 w3c#95
w3c#93 Clarified onerror usage in sender and receiver objects, as noted in: w3c#95 Clarified SST-MS capability issue noted in: w3c#108 Clarification of send() and receive() usage as noted in: w3c#119 Changed ICE state diagram as noted in: w3c#122 Removed getParameters methods and changed send() method as noted in: w3c#136 Changed definition of framerateScale and resolutionScale as noted in: w3c#137 Substituted "muxId" for the "receiverId" as noted in: w3c#138 w3c#140 Clarified the setting of track.kind as described in: w3c#141 Added SSRC conflict event to the RTCRtpSender, as described in: w3c#143 Addressed the "end of candidates" issues noted in: w3c#142 w3c#144