- From: Greg Billock <gbillock@google.com>
- Date: Thu, 19 Sep 2013 15:51:03 -0700
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: Jim Barnett <Jim.Barnett@genesyslab.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
- Message-ID: <CAAxVY9cC_g8Omi8S8QueXPbb36YWRfYxPwmHkwswZdBE63CXxw@mail.gmail.com>
Oops. Sorry. The TR is a bit more explicit about this: A MediaStream object is said to be finished when all tracks belonging to the stream have ended. When this happens for any reason other than the stop() method being invoked, the user agent must queue a task that runs the following steps: If the object's ended attribute has the value true already, then abort these steps. (The stop() method was probably called just before the stream stopped for other reasons, e.g. the user clicked an in-page stop button and then the user agent provided stop button.) Set the object's ended attribute to true. Fire a simple event named ended at the object. --- It clearer now than before that the spec means the 'ended' event does not happen if stop() is called. I think MediaRecorder should follow the same names and semantics. On Thu, Sep 19, 2013 at 3:38 PM, Harald Alvestrand <harald@alvestrand.no>wrote: > On 09/19/2013 10:50 PM, Greg Billock wrote: > > On Thu, Sep 19, 2013 at 1:33 PM, Jim Barnett <Jim.Barnett@genesyslab.com>wrote: > >> The stop event is the event that fires whenever recording ends. It’s >> not tied to the stop() function. So it’s just a question of what it should >> be called. >> > > That's what I interpreted the current language was trying to do, modulo > some typos. I think 'ended' is more consistent with other webrtc elements, > though. > > > Reading > http://www.w3.org/TR/2012/WD-mediacapture-streams-20120628/#widl-MediaStream-onended, > I see this: > > > Oops - can you please use the last published version at http://www.w3.org/TR/mediacapture-streams/ > ? <http://www.w3.org/TR/mediacapture-streams/> > > Or even the editor's one at > http://dev.w3.org/2011/webrtc/editor/getusermedia.html ? > > (at the moment they're the same, even though the published one has a date > 4 days after the editor's draft, which might be a little confusing. Usually > the editor's draft has the latest date.) > > You're referring to a version that is more than 12 months out of date. > >
Received on Thursday, 19 September 2013 22:51:30 UTC