W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [Bug 11348] New: [IndexedDB] Overhaul of the event model

From: Jonas Sicking <jonas@sicking.cc>
Date: Sat, 19 Feb 2011 20:46:55 -0800
Message-ID: <AANLkTikqY0sHvwZcPMF5r8Wx3geS_-fQcQSNOefp5jSM@mail.gmail.com>
To: Jeremy Orlow <jorlow@chromium.org>
Cc: David Grogan <dgrogan@chromium.org>, public-webapps@w3.org
On Fri, Feb 18, 2011 at 5:58 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> If an exception is unhanded in an IDB event handler, we abort the
> transaction.  Should we continue firing the other handlers when this
> happens, though?

What do you mean by "other handlers"? The other handlers for that same
event? If so, I would say we should so that we're sticking with the
DOM Events spec.

> And should preventDefault prevent the abort?

preventDefault usually prevents the default action of the event. The
abort isn't the default action, so I would say no. (It also seems a
bit weird that calling preventDefault on a success event would prevent
an abort).

/ Jonas
Received on Sunday, 20 February 2011 04:47:59 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT