[mediacapture-record] Should start() fire start before data is received by the recorder?

SingingTree has just created a new issue for https://github.com/w3c/mediacapture-record:

== Should start() fire start before data is received by the recorder? ==
The current wording of `start()` includes the following:

> Once media becomes available from one or more of the stream's tracks, start gathering the data into a Blob blob and queue a task, using the DOM manipulation task source, to fire an event named start at target. 

This suggests that the start event should not be fired until data is received. However, current implementations appear to differ in how they behave. When recording from an empty stream Chromium looks to immediately fire the start event, while Firefox will not. [Fiddle of this example](https://jsfiddle.net/SingingTree/arh7t487/).

Is there a preferred approach? Is there a function to waiting until data has arrived before firing start?

Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/133 using your GitHub account

Received on Thursday, 31 August 2017 04:19:00 UTC