- From: Adam Bergkvist via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Jun 2015 08:50:19 +0000
- To: public-media-capture-logs@w3.org
adam-be has just created a new issue for
https://github.com/w3c/mediacapture-main:
== Order of events ('addtrack' and 'active') ==
(The below text is sent to the list)
Consider a case with an inactive MediaStream. For some reason, a new
'live' track is added to it by the user agent. This means that both an
'addtrack' and 'active' event must be fired at the stream. I don't
believe we have specified the order of these.
My proposal is that the 'addtrack and 'removestrack' events fire
before
'active' and 'inactive' in all such cases.
This means that the active attribute will be false when the 'addtrack'
handler is fired, but it's better than the other way around. And in
this
particular case, it's pretty easy to foresee the upcoming activity
change by looking at the readyState of the track.
See https://github.com/w3c/mediacapture-main/issues/201
Received on Thursday, 25 June 2015 08:50:21 UTC