W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: [Bug 10400] New: [IndexedDB] IDBCursor.continue should return an IDBRequest

From: Jeremy Orlow <jorlow@chromium.org>
Date: Thu, 19 Aug 2010 22:11:59 +0100
Message-ID: <AANLkTinkibrohgdWbpArVD6puAENwMaQAfxcan+LR=_R@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: public-webapps@w3.org
I updated the bug.

On Thu, Aug 19, 2010 at 9:53 PM, Jonas Sicking <jonas@sicking.cc> wrote:

> On Thu, Aug 19, 2010 at 1:34 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
> >> We also remove the return value from .continue() and make it "return
> >> void". It doesn't make sense to return a bool indicating if this was
> >> the last entry or not since we only know that information
> >> asynchronously.
> >
> > Do you have thoughts on whether it should return an IDBRequest object
> > though?  Obviously the request object it returns would be the same one
> > originally returned from .openCursor().  As I mentioned in my reply, I
> could
> > see it being confusing, but for completeness I wanted to hear your
> thoughts.
>
> I don't think we should return a request, even the existing one. I
> can't see an advantage, and it just risks making authors think that
> they have to reregister event handlers etc.
>
> / Jonas
>
Received on Thursday, 19 August 2010 21:12:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:40 GMT