W3C home > Mailing lists > Public > public-media-capture@w3.org > May 2013

questions about direct assignment

From: Jim Barnett <Jim.Barnett@genesyslab.com>
Date: Wed, 29 May 2013 17:47:17 +0000
To: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <57A15FAF9E58F841B2B1651FFE16D281042345@GENSJZMBX02.msg.int.genesyslab.com>
A few questions about direct assignment of MediaStreams to media elements:

1.       In the case of direct assignment, is currentSrc  null?   The HTML5 spec says that if currentSrc is null, there is no media resource, so there may be a problem lurking in here.

2.       The HMTL5 spec allows for both the 'src' attribute and <source> children to be specified, and says that if they both occur, src takes precedence.  Do we want want to be consistent with this and allow direct assignment to occur with 'src' and <source>?  (Direct assignment would take precedence.)

3.       For the purposes of cross-origin constraints, what is the origin of the MediaStream?

4.       Do we say that the Tracks in the MediaStream must also implement AudioTrack and VideoTrack interfaces in the HTML5 spec?  If we do say this, are the media element track interfaces available on MediaStreams that aren't being used with media elements?

-          Jim
Received on Wednesday, 29 May 2013 17:47:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:17 UTC