- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Oct 2012 03:31:12 +0000
- To: public-webrtc@w3.org
- Message-ID: <bug-19587-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19587
Priority: P2
Bug ID: 19587
CC: public-webrtc@w3.org
Assignee: public-webrtc@w3.org
Summary: change "DataChannelEvent" to "RTCDataChannelEvent"
Severity: normal
Classification: Unclassified
OS: Windows NT
Reporter: eric.sun@huawei.com
Hardware: PC
Status: NEW
Version: unspecified
Component: WebRTC API
Product: WebRTC Working Group
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
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Thursday, 18 October 2012 03:31:13 UTC