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 16108 - [IndexedDB] (editorial) bound(), lowerBound() and upperBound() have open mixed
Summary: [IndexedDB] (editorial) bound(), lowerBound() and upperBound() have open mixed
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-24 14:30 UTC by Odin Hørthe Omdal
Modified: 2012-03-07 02:21 UTC (History)
4 users (show)

See Also:

Attachments

Description Odin Hørthe Omdal 2012-02-24 14:30:06 UTC 
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.
Comment 1 Joshua Bell 2012-02-24 16:42:05 UTC 
Agreed, that tripped me up as well when I was first reading the spec.
Comment 2 Jonas Sicking (Not reading bugmail) 2012-03-07 02:21:42 UTC 
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.