W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2017

[webrtc-pc] RTCDataChannel close event not defined

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Mon, 30 Jan 2017 01:14:26 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-203911712-1485738865-sysbot+gh@w3.org>
aboba has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== RTCDataChannel close event not defined ==
The specification does not define the RTCDataChannel close event.  If 
it is intended to be modeled after websockets, it would look like 
this: 

[Constructor(DOMString type, optional CloseEventInit eventInitDict)]
interface CloseEvent : Event {
  readonly attribute boolean wasClean;
  readonly attribute unsigned short code;
  readonly attribute USVString reason;
};

dictionary CloseEventInit : EventInit {
  boolean wasClean = false;
  unsigned short code = 0;
  USVString reason = "";
};

The wasClean attribute must return the value it was initialized to. It
 represents whether the datachannel closed cleanly or not.

The code attribute must return the value it was initialized to. It 
represents the datachannel close code provided.

The reason attribute must return the value it was initialized to. It 
represents the datachannel connection close reason provided.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/1009 using your GitHub account
Received on Monday, 30 January 2017 01:14:33 UTC

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