W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > August 2012

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 03 Aug 2012 01:03:59 +0000
Message-Id: <E1Sx6J5-0006Mr-LL@jessica.w3.org>
To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681

--- Comment #3 from Joshua Bell <jsbell@chromium.org> 2012-08-03 01:03:59 UTC ---
(In reply to comment #2)
> TypeError exceptions should be considered WebIDL type conversion errors.
> Therefore, we should always assume they are fired first before DOM exceptions. 

Agreed - that matches the Chromium/WebKit implementation as well. Otherwise,
we're flexible on ordering, including...

> The only possible caveat is where we return TypeError for passing zero on the
> IDBCursor.advance method.  For this method, we can specify that TypeError
> should be thrown first.

If it helps I can document Chromium's current exception priority, but as I said
we're flexible.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 3 August 2012 01:04:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 3 August 2012 01:04:02 GMT