On Fri, Apr 12, 2013 at 8:42 PM, Adam Bergkvist <adam.bergkvist@ericsson.com > wrote: > I think the problem with the current solution is the ended state on > MediaStream. It's hard to come up with a natural definition since a stream > can have no tracks and live tracks could possibly be added after the stream > ends. The useful thing is the event. Couldn't we simply have an event that > indicates that all tracks, currently in the stream, have ended, and not set > any state? > You could, but you still have to define the behavior of a media element with a MediaStream source, so you still need to define some kind of ended state --- or else say that a media element with a MediaStream source never ends, which is very unintuitive since in practice MediaStreams do end. I think that, given many kinds of MediaStreams do actually end, not exposing that state because of weird edge cases is undesirable and will frustrate Web developers. How about defining ended-ness on a MediaStream be dependent on the type of MediaStream, and insist that an ended MediaStream never transitions to not-ended. For a default definition, say that a MediaStream is ended if at some point in its history it transitioned from having live tracks to having no live tracks. Rob -- q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Saturday, 13 April 2013 13:09:11 UTC