W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

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

From: Jeremy Orlow <jorlow@chromium.org>
Date: Mon, 27 Jun 2011 23:51:13 -0700
Message-ID: <BANLkTikGM4_KfKNP2kcz5M19YMD_pLk5Cw@mail.gmail.com>
To: Israel Hilerio <israelh@microsoft.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
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, 28 June 2011 06:51:49 GMT

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