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

Re: [IndexedDB] Reason for aborting transactions

From: Glenn Maynard <glenn@zewt.org>
Date: Wed, 9 Feb 2011 20:59:35 -0500
Message-ID: <AANLkTi=BMfOpL+jFmjikaTWDkXUTaH8xgn37SLkzqP-Q@mail.gmail.com>
To: ben turner <bent.mozilla@gmail.com>
Cc: Jeremy Orlow <jorlow@chromium.org>, Jonas Sicking <jonas@sicking.cc>, Cameron McCormack <cam@mcc.id.au>, public-webapps WG <public-webapps@w3.org>
On Wed, Feb 9, 2011 at 8:37 PM, ben turner <bent.mozilla@gmail.com> wrote:

> > Normal exceptions have error messages that are not consistient across
> > implementations and are not localized.  What's the difference?
>
> These messages aren't part of any exception though, it's just some
> property on a transaction object. (None of our DOM exceptions, IDB or
> otherwise, have message properties btw, they're only converted to some
> message if they make it to the error console).
>

FWIW, I think that any scripting error message useful to display on the
console is useful to make accessible from scripts, provided they don't
contain sensitive information, like database paths.  I often attach a global
error handler to window.onerror and send script errors to the server
automatically, which is indispensable for quickly discovering lurking bugs
on user systems.  This is particularly important if there's more specific
information in the message than the exception itself, which seems likely
with error codes like "internal error".

(It's somewhat frustrating when they come back localized, but bearable.)

-- 
Glenn Maynard
Received on Thursday, 10 February 2011 02:00:25 GMT

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