- From: Adam Bergkvist <adam.bergkvist@ericsson.com>
- Date: Fri, 1 Feb 2013 07:31:42 +0100
- To: "LiLi (Z)" <Li.NJ.Li@huawei.com>
- CC: Travis Leithead <travis.leithead@microsoft.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 2013-01-31 20:07, LiLi (Z) wrote:
> I guess you meant to add an attribute to the HTMLMediaElement interface:
>
> interface HTMLMediaElement : HTMLElement {
>
> …
>
> readonly attributeMediaStream mediaStream;
>
> };
>
> Given that this part has reached CR, I’m not sure how easy it is to
> propose new changes.
>
> On the other hand, we can do something like this if the above is not
> possible:
>
> interfaceMediaStreamTrackList {
> [...]
> };
Hi
We recently moved away from having a special object for holding the
tracks of a stream [1, 2].
Perhaps the approach Travis suggested is the most straight forward one.
A different approach, that doesn't add anything to the HTMLMediaElement
interface, is to use the media element as an argument to a function in
our API (like the canvas API does for rendering a video element on a
canvas). E.g. by overloading the MediaStream constructor to accept a
HTMLMediaElement as a source as well.
/Adam
[1] http://lists.w3.org/Archives/Public/public-webrtc/2012Nov/0030.html
[2] http://lists.w3.org/Archives/Public/public-webrtc/2012Nov/0076.html
Received on Friday, 1 February 2013 06:47:31 UTC