- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Oct 2012 03:38:21 +0000
- To: public-webrtc@w3.org
- Message-ID: <bug-19588-4991@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19588
Priority: P2
Bug ID: 19588
CC: public-webrtc@w3.org
Assignee: public-webrtc@w3.org
Summary: change "MediaStreamEvent" to "RTCMediaStreamEvent"
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
the same reason with RTCDataChannelEvent, and also keep the MediaStream
untouched.
//////////////////change begin//////////////////////////////////
13.2 RTCMediaStreamEvent
The addstream and removestream events use the RTCMediaStreamEvent interface.
Firing a stream event named e with a MediaStream stream 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
RTCMediaStreamEvent interface with the stream attribute set to stream, must be
created and dispatched at the given target.
[Constructor(DOMString type, RTCMediaStreamEventInit eventInitDict)]
interface RTCMediaStreamEvent : Event {
readonly attribute MediaStream? stream;
};
dictionary RTCMediaStreamEventInit : EventInit {
MediaStream stream;
};
13.2.1 Attributes
stream of type MediaStream, readonly, nullable
The stream attribute represents the MediaStream object associated with the
event.
13.2.2 Dictionary RTCMediaStreamEventInit Members
stream of type MediaStream
///////////////////change end///////////////////////////////////////
--
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:38:22 UTC