- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 6 Jun 2011 13:47:39 -0700
- To: Israel Hilerio <israelh@microsoft.com>
- Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Mon, Jun 6, 2011 at 10:20 AM, Israel Hilerio <israelh@microsoft.com> wrote: > What about this: > > The default value for the range will be null which implies: > IDBKeyRange.lower = undefined > IDBKeyRange.upper = undefined > IDBKeyRange.lowerOpen = false > IDBKeyRange.upperOpen = false Well, currently the cursor navigation spec text deals with null cursors rather than cursors such as the above one (which I think can't be constructed using our current API). So I'm concerned that that would introduce inconsistencies in the spec. But as long as you verify that the above text works both together with the text in the cursor navigation algorithm, as well the definition for being in a range, then I'm fine with the above. But I think it would be easier to just say that the default value for the range argument is null. / Jonas
Received on Monday, 6 June 2011 20:48:36 UTC