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 16233 - Wrong description for lowerBound() and upperBound() methods
Summary: Wrong description for lowerBound() and upperBound() methods
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: 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-03-06 02:19 UTC by Israel Hilerio [MSFT]
Modified: 2012-03-07 02:20 UTC (History)
4 users (show)

See Also:

Attachments

Description Israel Hilerio [MSFT] 2012-03-06 02:19:17 UTC 
The spec currently says:

* lowerBound - Creates and returns a new key range with lower set to lower, 
lowerOpen set to open, upper set to undefined and and upperOpen set to true.
* upperBound - Creates and returns a new key range with lower set to undefined, lowerOpen set to true, upper set to value and and upperOpen set to open.

It should say the following in order to match the interface definition (change lower to bound and value to bound, respectively):

* lowerBound - Creates and returns a new key range with lower set to bound, lowerOpen set to open, upper set to undefined and and upperOpen set to true.
* upperBound - Creates and returns a new key range with lower set to undefined, lowerOpen set to true, upper set to bound and and upperOpen set to open.
Comment 1 Jonas Sicking (Not reading bugmail) 2012-03-07 02:20:37 UTC 
Fixed:

http://dvcs.w3.org/hg/IndexedDB/rev/d98bd946a997