This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Direct assignment using srcObject should be added.
Verifying consensus: - The Media Capture and Streams spec should add a new component to the HTML media element interface: partial interface HTMLMediaElement { attribute MediaStream? srcObject; } - We keep the ObjectURL method for backwards compatibility Someone (Mozilla, who's implemented this?) should state what the effect on src is when srcObject is set, and vice versa.
I'm not sure we need to keep createObjectURL if it's only for backwards compatibility — the legacy doesn't seem to that big to make it worthwhile. If the two approaches are complementary, why not having the two, but otherwise, it seems confusing.
srcObject takes precedence over other sources ('src' and <source>). There are use-cases for making srcObject take a Blob and a MediaSource too.
Direct assignment has been added to the spec: http://dev.w3.org/2011/webrtc/editor/getusermedia.html#dom-mediastreamtrack-clone But with a buggy name for it: http://lists.w3.org/Archives/Public/public-media-capture/2013Jul/0002.html on a buggy interface (acknowledged by Adam http://lists.w3.org/Archives/Public/public-media-capture/2013Jul/0004.html )
Fixed in the latest editors draft