This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The helpful text on the IDBKeyRange bounds is contradicting itself. The attributes say that open==false includes the key into the range, whilst the functions say the opposite. http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#widl-IDBKeyRange-bound-static-IDBKeyRange-any-lower-any-upper-boolean-lowerOpen-boolean-upperOpen > Is the lower-bound value included in the key range. Defaults to false. Could maybe say this instead, to align with the attribute: > If false, the lower-bound value is included in the key range. Defaults to false. Or something along those lines.
Agreed, that tripped me up as well when I was first reading the spec.
Fixed: http://dvcs.w3.org/hg/IndexedDB/rev/d98bd946a997 I tried to be extra verbose so that you won't have to do double-negatives in your head.