You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You need to describe the circumstances under which error events will occur. Examples include DTLS transport and ICE transport.
The “onerror” interface is not defined correctly. There is no need of custom event here.
Same on the “onstatechange” and some other events. If custom event is needed, the spec can say, “Fire a trust event with the name statechange, that does not bubble and is not cancelable, that uses the StateChangedEvent interface.”
w3c#59
-Fixes for error handling, as described in Issue 75
w3c#75
- Fixes for miscellaneous NITs, as described in Issue 76
w3c#76
- Enable retrieval of the SSRC to be used by RTCP, as described in Issue 77
w3c#77
- Support for retrieval of audio and video capabilities, as described in Issue 81
w3c#81
- getStats interface updated, as described in Issue 82
w3c#82
- Partially addressed SVC issues described in Issue 83
w3c#83
- Partially addressed statistics update issues described in Issue 85
w3c#85
From Shijun Sun:
You need to describe the circumstances under which error events will occur. Examples include DTLS transport and ICE transport.
The “onerror” interface is not defined correctly. There is no need of custom event here.
Same on the “onstatechange” and some other events. If custom event is needed, the spec can say, “Fire a trust event with the name statechange, that does not bubble and is not cancelable, that uses the StateChangedEvent interface.”
getStats, RTCErrorCallback/failureCallback is not defined or used anywhere.
The text was updated successfully, but these errors were encountered: