W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2013

Re: [futures] Handling of exceptions in the "future wrapper callback" algorithm does not make it clear that they are in fact being caught

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 6 Jun 2013 11:43:31 +0100
Message-ID: <CADnb78hgh+Axc-A4ZQJ_=qfQWeLwX8-u3KTwBt1KgfBTp-ay=A@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "www-dom@w3.org" <www-dom@w3.org>
On Thu, May 30, 2013 at 10:28 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> The future wrapper callback algorithm does not clearly say that an exception
> thrown by invoking callback should not in fact be considered uncaught (e.g.
> should not be reported to window.onerror).
> We generally need a clearer definition of what makes things "uncaught".  :(

Agreed. I raised this issue a while ago. Per Allen
the situation should become better. We should either start re-using
that terminology directly or through some IDL bridge once ES6 hits
stable and update everything that is currently sketchy at best. I will
try to clarify the text meanwhile and a reminder to update it once the
aforementioned happens.

Received on Thursday, 6 June 2013 10:44:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:21 UTC