-Original Message-
From: Jonas Sicking [mailto:jo...@sicking.cc]
Sent: Monday, March 21, 2011 2:54 PM
>> On Mon, Mar 21, 2011 at 11:51 AM, Pablo Castro
>> wrote:
>> > The spec today requires that properties key paths point at need to be
>> > enumerated (see 3.1.2 "Object Store"). Any pa
On Mon, Mar 21, 2011 at 2:33 PM, Jeremy Orlow wrote:
> Indexing toString or general getters seems like a bad idea since they can
> run arbitrary code. Wouldn't removing the restriction allow for that?
No, they live on the prototype chain so they aren't cloned anyway.
Well.. depending on what yo
On Mon, Mar 21, 2011 at 11:51 AM, Pablo Castro
wrote:
> The spec today requires that properties key paths point at need to be
> enumerated (see 3.1.2 “Object Store”). Any particular reason for that? It
> would be reasonable to allow an index on say the “length” property of a
> string. Perhaps we’r
Indexing toString or general getters seems like a bad idea since they can
run arbitrary code. Wouldn't removing the restriction allow for that?
J
On Mon, Mar 21, 2011 at 11:51 AM, Pablo Castro
wrote:
> The spec today requires that properties key paths point at need to be
> enumerated (see 3.1.
The spec today requires that properties key paths point at need to be
enumerated (see 3.1.2 "Object Store"). Any particular reason for that? It would
be reasonable to allow an index on say the "length" property of a string.
Perhaps we're opening the door for too much, so I wanted to double check
