Actually, I think we should abandon codes entirely and use the new
mechanism that WebIDL uses.
I honestly have a bit of a hard time understanding the WebIDL spec,
but I believe the idea is to implement the proposal made in [1].
Basically rather than having .code we'd have .type, along with
interf
This came up today that I didn't remember having a conversation about it with
folks.
We currently have IDBDatabaseException with a some error codes as constants and
code/message properties. Looking at DOMException as defined in DOM Core [1], it
turns out that a) the pattern of the class is iden
