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

Re: [IndexedDB] Any particular reason built-in properties are not indexable?

From: Jeremy Orlow <jorlow@chromium.org>
Date: Mon, 21 Mar 2011 14:33:12 -0700
Message-ID: <AANLkTikv0WZFmH-yU-xW-yL6w-b0ojv74vf=DdH94WN5@mail.gmail.com>
To: Pablo Castro <Pablo.Castro@microsoft.com>
Cc: public-webapps WG <public-webapps@w3.org>
Indexing toString or general getters seems like a bad idea since they can
run arbitrary code.  Wouldn't removing the restriction allow for that?


On Mon, Mar 21, 2011 at 11:51 AM, Pablo Castro

>  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 so we make an explicit call one way or the other. Thoughts?
> Thanks
> -pablo
Received on Monday, 21 March 2011 21:34:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 11 February 2015 14:36:49 UTC