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

[Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order

From: <bugzilla@jessica.w3.org>
Date: Sat, 16 Mar 2013 11:25:57 +0000
To: public-webapps@w3.org
Message-ID: <bug-17681-2927-UDCxvk91Pt@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681

Jonas Sicking <jonas@sicking.cc> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #7 from Jonas Sicking <jonas@sicking.cc> ---
Reopening. This bug was specifically about specifying order between all
exception types. I agree that generally it doesn't matter which exception is
thrown, but if we don't think that should be defined, then we should mark this
bug WONTFIX rather than FIXED.

I do think it would be good to define all exception orders though.

One way to do it would be to have a global list that defines some sort of
priority based on exception type. So if both a TransactionInactiveError and a
ReadOnlyError test is failing, we always throw ReadOnlyError. And if
ReadOnlyError and DataError both are possible, then we throw DataError.

Or something like that.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 16 March 2013 11:25:58 GMT

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