Re: Expect behavior of calling stop before receiving the onstart event on MediaRecorder API?

On 12/09/2013 03:35 PM, Jim Barnett wrote:
>
> Why don’t  we just put “return and run the following  steps 
> asynchronously” before the phrase “wait until media becomes 
> available”?  (Maybe change it to “once media becomes available”).
>
That's one way to do it.
I generally find it easier to follow a description when something that 
happens "all the time" is clearly specified separately from what happens 
when you call a specific function, but I can see both arguments.

I'll leave that to the discretion of the editor.

WRT the "starting" state - the UA clearly needs to know whether it's 
fired the "start" event or not, so there has to be internal state. I 
don't have strong reasons to expose that to the application, really; it 
just seemed to make describing the state transitions easier. I'll leave 
that to the discretion of the editor too.