W3C home > Mailing lists > Public > public-media-capture@w3.org > December 2015

MediaStream Recording Error Event spec: help!

From: Miguel Casas <mcasas@google.com>
Date: Mon, 7 Dec 2015 16:22:25 -0800
Message-ID: <CAPUS084MKgXhV_3U3hROSUJxUfpg821Sn9u+UcXUvOB-cOb=Lw@mail.gmail.com>
To: Philip J├Ągenstedt <philipj@opera.com>, rlin@mozilla.com, public-media-capture@w3.org
Cc: Harald Alvestrand <hta@google.com>, Peter Beverloo <beverloo@google.com>
If you don't use MediaStream Recording, you can stop reading now :)

I filed https://github.com/w3c/mediacapture-record/issues/31 in the hope we
can concentrate there the discussion about the cleanup of the Error Event
in MediaStream Recording spec. I feel like I'm not knowledgeable about
which option is best, and I'm not sure the appropriate folks will get
pinged from GitHub, so please take a look and vote or propose a better
option. Basically:
- we don't like the current MediaRecorderErrorEvent
<http://w3c.github.io/mediacapture-record/MediaRecorder.html#MediaRecorderErrorEvent>,
because is an unnecessary extension to the Event abstraction.
- Philip proposed the least amount of code solution: firing a simple Error
Event and leaving the error detail in a DOMException in MediaRecorder
class. (But that' implies changes to Gecko).
- Blink implements the Spec as-is, but I'm happy to change it (and the
implementation is still in Experimental).
- from my lack of high level knowledge, I see that CustomEvent
<https://dom.spec.whatwg.org/#interface-customevent> would also fit the
bill?
M


-- 

Miguel Casas-Sanchez | Gatopardo del Software | ydog <ydog@google.com> /
mcasas@google.com | +1 (650) 603 1380
Received on Tuesday, 8 December 2015 10:35:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 8 December 2015 10:35:42 UTC