- From: Aaron Colwell <acolwell@google.com>
- Date: Thu, 5 Sep 2013 07:56:13 -0700
- To: Cyril Concolato <cyril.concolato@telecom-paristech.fr>
- Cc: "public-html-media@w3.org" <public-html-media@w3.org>
- Message-ID: <CAA0c1bAZck6NJwMxi69j7=SRJ39q828=3LcRGXsb_yGy8Xnzzg@mail.gmail.com>
I would be open to this change assuming that we nailed down what HTMLMediaElement.src & HTMLMediaElement.currentSrc were supposed to be when srcObject was set. Since there are already current implementations that implement createObjectURL out there, I don't think this mechanism will completely go away. We could definitely discourage its usage going forward though. Aaron On Thu, Sep 5, 2013 at 5:44 AM, Cyril Concolato < cyril.concolato@telecom-paristech.fr> wrote: > Hi all, > > It seems that many people in the WebApps WG think the use of > URL.createObjectURL should be avoided (see the thread here [1]). Given that > the Media Capture Task Force will be adding an srcObject attribute to the > HTMLMediaElement, shouldn't we use that too and deprecate (or discourage) > the use of URL.createObjectURL(**MediaSource)? > > Regards, > Cyril > > [1] http://lists.w3.org/Archives/**Public/public-webapps/** > 2013JulSep/0374.html<http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0374.html> > > -------- Message original -------- > Sujet: Extending createObjectUrl to MediaStream? > Date de renvoi : Wed, 28 Aug 2013 15:48:34 +0000 > De (renvoi) : public-webapps@w3.org > Date : Wed, 28 Aug 2013 17:48:15 +0200 > De : Dominique Hazael-Massieux <dom@w3.org> > Organisation : W3C > Pour : public-webapps@w3.org > Copie à : public-media-capture@w3.org > > > > > Hi WebApps WG, > > The Media Capture Task Force (responsible for specs that deal with > MediaStream objects [1]) has been considering whether one should be able > to assign a MediaStream to <video> and <audio> elements via an URL > obtained via createObjectURL or not, and is seeking feedback on the > question. > > More precisely: > A. we define a new srcObject attribute on HTMLMediaElement objects that > can take directly a MediaStream object and make it playable > video.srcObject = mediastream; > B. the spec also supports assigning a MediaStream via the src attribute, > via an URL obtained through createObjectURL: > video.src = URL.createObjectURL(**mediastream); > > While there are ongoing discussions on how to spec B properly [2] (which > will require coordination with the WebApps Working Group), we are first > and foremost wondering if that option is needed at all. > > We are thus looking for input on the use cases for createObjectURL as > used for the File API, and whether these use cases would also apply to > our MediaStream case. In general, is there a need for any object > readable by media elements to support an URL-based approach for > consistency with the rest of the platform? > > Thanks! > > Dom for capture-ACTION-23 > > 1. http://dev.w3.org/2011/webrtc/**editor/getusermedia.html<http://dev.w3.org/2011/webrtc/editor/getusermedia.html> > 2. https://www.w3.org/Bugs/**Public/show_bug.cgi?id=19594<https://www.w3.org/Bugs/Public/show_bug.cgi?id=19594> > > > > > > >
Received on Thursday, 5 September 2013 14:56:43 UTC