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

Categories

(Core :: Audio/Video: Recording, defect)

defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla26

People

(Reporter: jsmith, Assigned: rlin)

References

Details

(Whiteboard: [FT: Media Recording, Sprint])

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.
Blocks: 899878
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?
Flags: needinfo?(roc)
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.
Flags: needinfo?(roc)
This Bug 899935's patch would also fix this.
Depends on: 899935
Whiteboard: [FT: Media Recording, Sprint]
Fixed by the dependency. This is confirmed fixed with the mochitest included.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Target Milestone: --- → mozilla26
Component: Video/Audio → Video/Audio: Recording
No longer blocks: MediaRecording
You need to log in before you can comment on or make changes to this bug.