- From: Jan-Ivar Bruaroey <jib@mozilla.com>
- Date: Fri, 03 Oct 2014 10:44:59 -0400
- To: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
- Message-ID: <542EB66B.9090000@mozilla.com>
On 10/3/14, 5:13 AM, Harald Alvestrand wrote:
> Based on this stuff finally happening, I propose that we change our
> definition:
>
> [NoInterfaceObject]
> interfaceMediaStreamError {
> readonly attributeDOMString name <http://w3c.github.io/mediacapture-main/getusermedia.html#widl-MediaStreamError-name>;
> readonly attributeDOMString? message <http://w3c.github.io/mediacapture-main/getusermedia.html#widl-MediaStreamError-message>;
> readonly attributeDOMString? constraintName <http://w3c.github.io/mediacapture-main/getusermedia.html#widl-MediaStreamError-constraintName>;
> };
>
> to read
>
> [NoInterfaceObject]
> interfaceMediaStreamError : Error {
> readonly attributeDOMString? constraintName <http://w3c.github.io/mediacapture-main/getusermedia.html#widl-MediaStreamError-constraintName>;
> };
Looks great!
One question, we define three of our errors (NotSupportedError,
NotFoundError and AbortError) as "same as DOM4" [1], but they're just
namesakes. i.e. they're of type MediaStreamError, not DOMException they
way the prose is written. Just doublechecking that that's what we want,
or was the intent to return errors more identical to DOM (i.e. create
errors of type DOMException for those)? - FWIW I think I prefer
MediaStreamError, just unsure curious what the redirect is supposed to
buy us?
[1]
http://w3c.github.io/mediacapture-main/archives/20140909/getusermedia.html#error-names
.: Jan-Ivar :.
Received on Friday, 3 October 2014 14:45:26 UTC