- From: Jeremy Orlow <jorlow@chromium.org>
- Date: Mon, 7 Mar 2011 22:21:25 -0800
- To: public-webapps WG <public-webapps@w3.org>
Received on Tuesday, 8 March 2011 06:22:17 UTC
As far as I recall, we never settled on how key path should be specified. Right now in Chrome, we allow any combination of .'s and static array lookups. So, for example, we allow "foo.bar[1][2].baz". I don't remember any specific use cases for the array lookups though, so I'm wondering if we should just specify "<property> ["." <property>]*" to be the key path specification. Where <property> is whatever's allowed in JavaScript. It seems to me that this should support most use cases, should be easy to understand and implement, and should leave us a lot of flexibility to support other use cases as we may come up with them. Thoughts? J
Received on Tuesday, 8 March 2011 06:22:17 UTC