Closed
Bug 934818
Opened 11 years ago
Closed 9 years ago
[MediaRecorder TEST] MediaRecorder should dispatch onstop event after source media stream finished
Categories
(Core :: Audio/Video: Recording, defect, P3)
Core
Audio/Video: Recording
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: u459114, Unassigned)
References
(Blocks 1 open bug)
Details
Take audio element as source, take capture stream from this element and create a media recorder with this stream.
After this media stream finish playback, media recorder should send out onstop state "automatically".
Meanwhile, call requestData/stop/ start at this moment should get DOM InvalidState error.
The same for MediaStreamDestination which generate from an AudioContext
Updated•11 years ago
|
Comment 1•11 years ago
|
||
Is captureStream() or captureStreamUntilEnded() called?
https://dvcs.w3.org/hg/audio/raw-file/tip/streams/StreamProcessing.html#media-elements 3.1
"The captureStream() method returns a new MediaStream that plays the same audio and video as stream. captureStream() sets the audioCaptured attribute to true."
"The captureStreamUntilEnded() method returns a new MediaStream that plays the same audio and video as stream, until the element next reaches the "ended playback" state, at which point this stream will enter the finished state. captureStreamUntilEnded() sets the audioCaptured attribute to true."
It looks like only the stream returned by captureStreamUntilEnded() could enter the finished state, if I read it correctly.
Updated•11 years ago
|
Assignee: nobody → rlin
Updated•11 years ago
|
Component: Video/Audio → Video/Audio: Recording
Summary: [MedaiRecorder TEST] MediaRecorder should dispatch onstop event after source media stream finished → [MediaRecorder TEST] MediaRecorder should dispatch onstop event after source media stream finished
Updated•9 years ago
|
Priority: -- → P3
Comment 3•9 years ago
|
||
I believe now the onstop event will dispatch to JS when stream ended.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•