W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2016

[webrtc-pc] NetworkError event is not defined and might not be needed

From: ShijunS via GitHub <sysbot+gh@w3.org>
Date: Mon, 29 Feb 2016 17:54:04 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-137324409-1456768443-sysbot+gh@w3.org>
ShijunS has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== NetworkError event is not defined and might not be needed ==
When discussing the following portion of Section 6.2 in issue #492

>  1. ...
>  2. Set channel's readyState attribute to closed.
>  3. If the transport was closed with an error, fire an NetworkError 
event at channel.
>  4. Fire a simple event named close at channel

@adam-be commented 

> This one is a bit strange. Is the "NetworkError event" even defined 
somewhere? I think we could do with one event here.

I'm opening a new issue to track this.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/526 using your GitHub account
Received on Monday, 29 February 2016 17:54:05 UTC

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