Re: [indexeddb] transaction commit failure from Shawn Wilsher on 2011-08-16 (public-webapps@w3.org from July to September 2011)

From: Shawn Wilsher <me@shawnwilsher.com>
Date: Mon, 15 Aug 2011 20:27:00 -0700
To: public-webapps@w3.org
Message-ID: <4E49E384.9040908@shawnwilsher.com>

On 8/15/2011 3:31 PM, Israel Hilerio wrote:
> When the db is doing a commit after processing all records on the
> transaction, if for some reason it fails, should we produce an error
> event first and let the bubbling produce a transaction abort event or
> should we only produce a transaction abort event. It seems that doing
> the first approach would be more complete.
I agree; the first approach seems better and I can't think of any reason 
why it would be difficult to implement.

The catch is that calling `preventDefault` will not prevent the abort, 
which is (I think) different from how we handle other errors, right?

Cheers,

Shawn

Received on Tuesday, 16 August 2011 03:27:26 UTC