19587 2012-10-18 03:31:12 +0000 change "DataChannelEvent" to "RTCDataChannelEvent" 2012-10-25 00:29:25 +0000 1 1 1 Unclassified WebRTC Working Group WebRTC API unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 eric.sun public-webrtc fluffy public-webrtc oldest_to_newest 76550 0 eric.sun 2012-10-18 03:31:12 +0000 datachannel is only used by peerconnection, we should add RTC-prefix before datachannelevent to comply with RTCPeerConnectionIceEvent. As for DataChannel, we keep it untill we decide to change it. ///////////////////////////////////////////////////////// 13.3 RTCDataChannelEvent The datachannel event use the RTCDataChannelEvent interface. Firing a datachannel event named e with a DataChannel channel means that an event with the name e, which does not bubble (except where otherwise stated) and is not cancelable (except where otherwise stated), and which uses the RTCDataChannelEvent interface with the channel attribute set to channel, must be created and dispatched at the given target. [Constructor(DOMString type, RTCDataChannelEventInit eventInitDict)] interface RTCDataChannelEvent : Event { readonly attribute DataChannel channel; }; dictionary RTCDataChannelEventInit : EventInit { DataChannel channel; }; 13.3.1 Attributes channel of type DataChannel, readonly The channel attribute represents the DataChannel object associated with the event. 13.3.2 Dictionary RTCDataChannelEventInit Members channel of type DataChannel 77058 1 fluffy 2012-10-24 19:20:53 +0000 has this been fixed? 77074 2 eric.sun 2012-10-25 00:29:25 +0000 Yes, from latest specification, we can see, this bug has been fixed. thanks (In reply to comment #1) > has this been fixed?