W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

[Bug 19450] New: [IndexedDB] Key path segments should permit reserved words

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Oct 2012 20:57:35 +0000
To: public-webapps@w3.org
Message-ID: <bug-19450-2927@http.www.w3.org/Bugs/Public/>

          Priority: P2
            Bug ID: 19450
                CC: mike@w3.org, public-webapps@w3.org
          Assignee: dave.null@w3.org
           Summary: [IndexedDB] Key path segments should permit reserved
        QA Contact: public-webapps-bugzilla@w3.org
          Severity: minor
    Classification: Unclassified
                OS: All
          Reporter: jsbell@chromium.org
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: Indexed Database API
           Product: WebAppsWG

In the IDB spec the definition of a valid key path is built around:

A DOMString containing a JavaScript identifier [ECMA-262].

... plus dotted combinations of identifiers and arrays thereof.

ECMA-262 gives:

Identifier ::
  IdentifierName but not ReservedWord

IdentifierName ::
  IdentifierName IdentifierPart

And defines ReservedWord as:

ReservedWord ::

Keyword :: one of
  break do instanceof typeof case else new var ...

This would appear to preclude key paths such as:


Neither FF nor Chrome appear to reject such key paths.

I suggest the IDB spec be updated to refer specifically to the IdentifierName
production in ECMA-262.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 10 October 2012 20:57:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 14:37:01 UTC