W3C home > Mailing lists > Public > public-media-capture@w3.org > October 2014

Fwd: [Bug 23367] Move exceptions into IDL

From: Harald Alvestrand <harald@alvestrand.no>
Date: Fri, 03 Oct 2014 11:13:11 +0200
Message-ID: <542E68A7.10307@alvestrand.no>
To: "public-media-capture@w3.org" <public-media-capture@w3.org>
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>;
};

as soon as the editors can verify that following the "WebIDL" link in 
our spec leads to a document that has incorporated the change quoted below.
(At the moment the link points to the 19 April 2012 Candidate 
Recommendation).

This should lead to no change in actual behaviour of existing JS code, 
unless they inspect the prototype chain of MediaStreamError objects 
(which seems an odd thing for anything but conformance tests to do).


-------- Videresendt melding --------
Emne: 	[Bug 23367] Move exceptions into IDL
Dato: 	Fri, 03 Oct 2014 05:34:37 +0000
Fra: 	bugzilla@jessica.w3.org
Til: 	harald@alvestrand.no



https://www.w3.org/Bugs/Public/show_bug.cgi?id=23367

Cameron McCormack <cam@mcc.id.au> changed:

            What    |Removed                     |Added
----------------------------------------------------------------------------
              Status|NEW                         |RESOLVED
          Resolution|---                         |FIXED

--- Comment #8 from Cameron McCormack <cam@mcc.id.au> ---
I've removed IDL exception definitions, moved DOMException into the spec
(including the table of names and legacy codes), and added types to refer to
them -- Error for any exception type (including the native ECMAScript Error
objects) and DOMException for just DOMExceptions.  I also made
DOMException.[[Prototype]] == Error.prototype.

https://github.com/heycam/webidl/commit/50e172ec079db073c3724c9beac1b576fb5dbc47

http://heycam.github.io/webidl/#idl-exceptions
http://heycam.github.io/webidl/#idl-Error
http://heycam.github.io/webidl/#idl-DOMException
http://heycam.github.io/webidl/#es-Error
http://heycam.github.io/webidl/#es-DOMException
http://heycam.github.io/webidl/#es-exceptions
http://heycam.github.io/webidl/#es-exception-objects
http://heycam.github.io/webidl/#es-creating-throwing-exceptions

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 3 October 2014 09:13:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:30 UTC