Closed
Bug 970772
Opened 11 years ago
Closed 7 years ago
Media Recording - Errors fired from an onerror callback always fire GenericError, which provide no context of the problem
Categories
(Core :: Audio/Video: Recording, defect, P2)
Core
Audio/Video: Recording
Tracking
()
RESOLVED
DUPLICATE
of bug 1275856
People
(Reporter: jsmith, Unassigned)
Details
Currently, if the media recorder hits an error during recording, an onerror callback will be fired with an object that has the name "GenericError." From a developer's perspective, this isn't that useful - it doesn't provide any context of the problem. We should improve our error messages here to indicate what actually failed when onerror fires from a media recording object.
Reporter | ||
Updated•11 years ago
|
Blocks: MediaRecording
Comment 1•11 years ago
|
||
We may attach the message in RecordErrorEvent through onError event.
The error messages also involve localization problem.
BTW, That topic is still unclear in w3c spec.
Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Randy Lin [:rlin] from comment #1)
> We may attach the message in RecordErrorEvent through onError event.
> The error messages also involve localization problem.
> BTW, That topic is still unclear in w3c spec.
How would I access the message? I didn't see the message property on the object when I inspected in the console. I've only seen the "GenericError" portion of it.
Comment 3•11 years ago
|
||
We have not added it yet.
Updated•11 years ago
|
Component: Video/Audio → Video/Audio: Recording
Reporter | ||
Updated•11 years ago
|
No longer blocks: MediaRecording
Updated•9 years ago
|
Rank: 25
Priority: -- → P2
Comment 4•9 years ago
|
||
Beyond the lack of context, our code's RecordErrorEvent has a lone .name property [1] which is not to spec.
Spec says it should have an .error property instead, among other things [2].
[1] http://mxr.mozilla.org/mozilla-central/source/dom/webidl/RecordErrorEvent.webidl#8
[2] https://w3c.github.io/mediacapture-record/MediaRecorder.html#errorevent
Bug 1275856 should address the issues noted in comment 4. We should also be providing a JS stack trace where possible. I'm in favour of closing this as the specific issues here have been addressed. :jib, yay/nay?
Flags: needinfo?(jib)
Comment 6•7 years ago
|
||
I agree.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jib)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•