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

RE: [indexeddb] Behavior when calling IDBCursor.continue multiple times

From: Israel Hilerio <israelh@microsoft.com>
Date: Tue, 12 Jul 2011 23:55:55 +0000
To: Jonas Sicking <jonas@sicking.cc>, Eliot Graff <Eliot.Graff@microsoft.com>
CC: Jeremy Orlow <jorlow@chromium.org>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <F695AF7AA77CC745A271AD0F61BBC61E3D191DF1@TK5EX14MBXC119.redmond.corp.microsoft.com>
I see what you're saying.

What we originally wanted to convey was that calling this method consecutively or in a row within the same onsuccess handler is not allowed.  This assumed the success handler was not invoked in between these calls.
Would something similar to what I just wrote be enough to clarify the statement?

Israel

On Monday, July 11, 2011 9:24 PM, Jonas Sicking wrote:
> Hmm.. The fix here is somewhat unclear. Obviously you're allowed to call
> .continue multiple times if a "success" event fires in between.
> 
> The very first sentence in the definition for .continue reads:
> 
> "If this cursor's got value flag is false, this method throws a
> NOT_ALLOWED_ERR".
> 
> Was this not enough?
> 
> I'd be fine with keeping the current sentence, but it would need to be clarified
> to make it clear that .continue() can be called multiple times if "success" fires
> in between, and that "success" event doesn't represent reaching the end of
> the cursor. Or something to that extent.
> 
> / Jonas
> 
> On Thu, Jul 7, 2011 at 3:32 PM, Eliot Graff <Eliot.Graff@microsoft.com> wrote:
> > For both IDBCursor.continue and IDBCursorSync.continue,
> >
> > Added one paragraph to the description:
> > If you call this method multiple times, the cursor throws a
> NOT_ALLOWED_ERR exception and does not continue. If you catch the error
> you can then iterate through the cursor normally.
> >
> > Standardized the wording in the async and sync NOT_ALLOWED_ERR
> description to be:
> > The cursor is currently being iterated, or has iterated past its end.
> >
> > Eliot
> >
> > From: public-webapps-request@w3.org
> > [mailto:public-webapps-request@w3.org] On Behalf Of Jeremy Orlow
> > Sent: Monday, June 27, 2011 11:51 PM
> > To: Israel Hilerio
> > Cc: public-webapps@w3.org
> > Subject: Re: [indexeddb] Behavior when calling IDBCursor.continue
> > multiple times
> >
> > I thought it already was in there (or in some bug).  But, if not, yeah it should
> just be documented.
> > On Thu, Jun 23, 2011 at 2:32 PM, Israel Hilerio <israelh@microsoft.com>
> wrote:
> > We noticed that the spec doesn't say anything about what needs to happen
> if IDBCursor.continue is called multiple times.  We noticed that both FF and
> Chrome throw a NOT_ALLOWED_ERR exception.  If the exception is not
> caught, the cursor doesn't continue to iterate, an error event is triggered
> (errorCode = ABORT_ERR), and the transaction is aborted.  However, if the
> exception is caught, the cursor will iterate normally.  This model makes sense
> to us.
> >
> > It seems this is something we should document on the spec.  Do you agree?
> >
> > Israel
> >
> >
> >
Received on Tuesday, 12 July 2011 23:56:23 GMT

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