Re: [IndexedDB] Reason for aborting transactions

On Fri, Jan 28, 2011 at 2:35 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> Given that transactions can be aborted because of explicit action, internal
> errors, quota errors, and possibly other things in the future, I'm wondering
> if we should add some way for people to find out why the transaction was
> aborted.
> Thoughts?

Hmm.. not a bad idea. We also abort transactions if the user leaves
the current page in the middle of a transaction. Don't remember if the
spec requires this or not, but it might make sense to do so.

/ Jonas