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: Wed, 5 Jun 2013 14:10:58 +0100
Message-ID: <CADnb78jKWN2FsZZUuCRebsK2eDbjnBJ6ioz8jTPqG91bWgAQDw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: "www-dom@w3.org" <www-dom@w3.org>
On Tue, Jun 4, 2013 at 6:47 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 6/4/13 11:19 AM, Domenic Denicola wrote:
>> Really? To JavaScript programmers, it's the only thing that makes sense.
>> There is no way in native JavaScript semantics to do the magic thing the web
>> platform currently does, wherein (a) code is executed synchronously, but (b)
>> exceptions thrown from that code bypass any surrounding `try`/`catch`
>> blocks, and instead reach `window.onerror`.
>
> Uh... Sure there is.  It's as simple as a function that catches the
> exception and then calls window.onerror, no?

Given the likely outcome of
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22185 running the
script as a fresh code entry-point is a special kind of semantics, I
think. When TC39 tries to rationalize script execution they'll have to
take this into account (among many other things).


--
http://annevankesteren.nl/
Received on Wednesday, 5 June 2013 13:11:29 UTC

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