- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Fri, 29 Aug 2014 11:13:10 -0700
- To: Harald Alvestrand <harald@alvestrand.no>
- Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
Seems basically like a good idea. Did you have any ideas on what this "error" attribute might contain? A DOMString is OK for debugging, but an enumeration permits programmatic interaction. If you go for an enumeration, a "cause" attribute might be better, so that you can include things like "remote peer stopped sending", "local source stopped", and "reached end of input source", all of which might be non-error cases. On 29 August 2014 04:45, Harald Alvestrand <harald@alvestrand.no> wrote: > MediaStreamErrorEvent Maybe MediaStreamEndedEvent so that you don't have to explain why an event with Error in its name is being generated in non-error situations.
Received on Friday, 29 August 2014 18:13:38 UTC