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

Re: Exceptions in event listeners triggered by dispatchEvent().

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 3 Jun 2013 10:33:37 +0100
Message-ID: <CADnb78ggmfqpbzY3D2-WVDuz4GNs7=GWvm5GFLLd0KCjtvGGMw@mail.gmail.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: johnjbarton <johnjbarton@chromium.org>, "www-dom@w3.org" <www-dom@w3.org>
On Sun, Jun 2, 2013 at 7:10 PM, Glenn Maynard <glenn@zewt.org> wrote:
> I think exceptions from callbacks are handled explicitly in specs, eg. by
> saying something like "if the called function throws an exception, ...".
> Since the "invoke the event listeners" algorithm (step 4.7) doesn't say to
> do anything with exceptions, that means that nothing must be done with them,
> eg. discard them.  (Anne: correct?)  Maybe this could use a note, though.

It should reach window.onerror. Allan introduced new language
constructs in ES6 for this. I'm hoping that WebIDL/JSIDL will adopt
these and make them available to platform APIs (or platform APIs
should reference them directly, however we end up resolving that).
Then it should all be a bit clearer which exceptions propagate and
which are only for window.onerror.

Received on Monday, 3 June 2013 09:34:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:02 UTC