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

[Bug 15987] New: [IndexedDB] Invalid dates should not be valid keys

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Feb 2012 19:45:33 +0000
To: public-webapps@w3.org
Message-ID: <bug-15987-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15987

           Summary: [IndexedDB] Invalid dates should not be valid keys
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jsbell@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


Section 3.1.3 Keys:

"... A value is said to be a valid key if it is one of the following types:
Array JavaScript objects [ECMA-262], DOMString [WEBIDL], Date [ECMA-262] or
float [WEBIDL]. ... Additionally, if the value is of type float, it is only a
valid key if it is not NaN. Conforming user agents must support all valid keys
as keys."

Just as NaN floats are not valid keys, invalid dates - i.e. dates where the
internal double (revealed by date.valueOf()) is NaN - should not be considered
valid keys as these cannot be "compared to other Date values chronologically"

-- 
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 Tuesday, 14 February 2012 19:45:35 GMT

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