https://www.w3.org/Bugs/Public/show_bug.cgi?id=19450
Priority: P2
Bug ID: 19450
CC: [email protected], [email protected]
Assignee: [email protected]
Summary: [IndexedDB] Key path segments should permit reserved
words
QA Contact: [email protected]
Severity: minor
Classification: Unclassified
OS: All
Reporter: [email protected]
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 ::
IdentifierStart
IdentifierName IdentifierPart
(etc)
And defines ReservedWord as:
ReservedWord ::
Keyword
FutureReservedWord
NullLiteral
BooleanLiteral
Keyword :: one of
break do instanceof typeof case else new var ...
(etc)
This would appear to preclude key paths such as:
"foo.delete.bar"
"my.public.data"
"response.true.details"
"options.null"
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.
