This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11375 - [IndexedDB] Error codes need to be assigned new numbers
Summary: [IndexedDB] Error codes need to be assigned new numbers
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jeremy Orlow
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2010-11-22 12:43 UTC by Jeremy Orlow
Modified: 2011-03-08 01:19 UTC (History)
2 users (show)

See Also:


Description Jeremy Orlow 2010-11-22 12:43:09 UTC
The error codes specced in IDBDatabaseException's interface need to be redone.  They currently overlap with existing exception error codes and use 0 which we've avoided using in the past [0].  In addition, the codes are non-contiguous which also seems to be non-standard.  We should re-map the exception numbers into something contiguous that doesn't overlap with other exception codes.

[0] I'm not sure if 0 is actually specced to be reserved, but in practice it seems to be.  And WebKit uses 0 internally to signal "no exception".
Comment 1 Jeremy Orlow 2011-03-08 01:19:26 UTC
This was somewhat done at some point.  And any further cleanup should probably wait until exception/error stuff upstream in WebIDL is settled.