Closed Bug 902318 Opened 8 years ago Closed 8 years ago
Media Recording - Calling start() and stop() in fast succession fails to fire ondataavailable & onstop events
STR 1. Apply the patch from https://bug899878.bugzilla.mozilla.org/attachment.cgi?id=786738 2. Run the mochitest Expected ondataavailable & onstop should fire in succession. Actual ondataavailable & onstop fail to fire.
Assignee: nobody → rlin
Hmm...I'm now debating what the right behavior here is. So in this scenario I've called stop() right after calling start(), which likely implies we've generated no data in the blob from recording. Does that imply that ondataavailable should still fire, except with a blob size of zero?
According to the spec, we should fire an event with a blob size of zero, yes. We might as well do that, it's a bit more predictable.
Fixed by the dependency. This is confirmed fixed with the mochitest included.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Video/Audio → Video/Audio: Recording
You need to log in before you can comment on or make changes to this bug.