- From: Glenn Adams <glenn@skynav.com>
- Date: Wed, 6 Feb 2013 15:50:56 -0700
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-media-capture@w3.org
- Message-ID: <CACQ=j+exe+ujhsuW7dHiiMLf37SWy16N_-hfS0ASuU-E_uUrdg@mail.gmail.com>
This needs to be coordinated with the HTML MSE spec: https://dvcs.w3.org/hg/html-media/raw-file/default/media-source/media-source.html On Wed, Feb 6, 2013 at 2:48 PM, Dominique Hazael-Massieux <dom@w3.org>wrote: > Hi, > > The latest editors draft of getUserMedia still uses URL.createObjectURL > to assign the content of a media stream to an HTML media element > (<audio> and <video>): > > http://dev.w3.org/2011/webrtc/editor/getusermedia.html#mediastreams-as-media-elements > > My understanding is that we had converged towards instead use a new > attribute on the HTMLMediaElement interface, srcObject, to which a > MediaStream could be directly assigned. > > Is that indeed the case (in which case I hope the editors draft can be > updated to reflect this)? If not, I think this needs to be settled with > relatively high priority since it's certainly one points where current > implementations of getUserMedia diverges, and that any developer using > the API is going to hit almost immediately. > > Practically speaking, while we could simply define a partial interface > to add srcObject to HTMLMediaElement, it's likely something where we > would want to coordinate with the HTML Working Group. > > Thanks, > > Dom > > > >
Received on Wednesday, 6 February 2013 22:51:45 UTC