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****
>