W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

[Bug 16108] New: [IndexedDB] (editorial) bound(), lowerBound() and upperBound() have open mixed

From: <bugzilla@jessica.w3.org>
Date: Fri, 24 Feb 2012 14:30:07 +0000
To: public-webapps@w3.org
Message-ID: <bug-16108-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16108

           Summary: [IndexedDB] (editorial) bound(), lowerBound() and
                    upperBound() have open mixed
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: odinho@opera.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 24 February 2012 14:30:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT