W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2013

[Bug 22522] WebIDL, error handling, and promises

From: <bugzilla@jessica.w3.org>
Date: Sun, 08 Dec 2013 07:33:14 +0000
To: public-script-coord@w3.org
Message-ID: <bug-22522-3890-SeTePsgnJ3@http.www.w3.org/Bugs/Public/>

Domenic Denicola <domenic@domenicdenicola.com> changed:

           What    |Removed                     |Added
                 CC|                            |domenic@domenicdenicola.com

--- Comment #9 from Domenic Denicola <domenic@domenicdenicola.com> ---
So, we need to fix WebIDL so that whenever an error is implicitly thrown (e.g.
in the overload resolution algorithm, or maybe other places) by a
Promise-returning function, it needs to automatically translate that to
rejecting the returned promise. E.g. if I do

Promise doSomethingAsync(DOMString arg) // non-optional

var p = doSomethingAsync();

then p should be a Promise rejected with a TypeError, and a TypeError should
not have been thrown.

Should we use this bug for tracking that?

You are receiving this mail because:
You are on the CC list for the bug.
Received on Sunday, 8 December 2013 07:33:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:19 UTC