- From: Miguel Casas-Sanchez via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Dec 2016 21:52:43 +0000
- To: public-media-capture-logs@w3.org
Merging #31 into this issue. The Spec currently defines an [`ErrorEvent`](https://w3c.github.io/mediacapture-record/MediaRecorder.html#errorevent) that just acts as a holder for a `DOMException`. Gecko defines a RecordErrorEvent [1] that is used in MediaRecorder.cpp [2] by filling its name in NotifyError() to e.g. SecurityError, OutOfMemoryError or otherwise GenericError. Chromium has no specific error. Coalescing other conversations: - using [`ErrorEvent`](https://html.spec.whatwg.org/multipage/webappapis.html#the-errorevent-interface) is not a good idea here because of the `filename`, `lineno` and `colno` that hints as to it being an error produced in a file; - we still would like to produce an Error Event interface with a `message` field; - I personally think it'd be an overkill to define a sort-of `MediaRecorderErrorEvent` just to add a `DOMString` message field. @jan-ivar, @foolip, what would you suggest we do? [1] https://github.com/mozilla/gecko-dev/blob/master/dom/webidl/RecordErrorEvent.webidl [2] https://github.com/mozilla/gecko-dev/blob/master/dom/media/MediaRecorder.cpp#L1385 -- GitHub Notification of comment by miguelao Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/53#issuecomment-268650687 using your GitHub account
Received on Wednesday, 21 December 2016 21:52:53 UTC