Updated the spec with Jonas' wording.
Thanks!
Eliot
-Original Message-
From: Israel Hilerio
Sent: Tuesday, July 12, 2011 6:25 PM
To: Jonas Sicking
Cc: Eliot Graff; Jeremy Orlow; public-webapps@w3.org
Subject: RE: [indexeddb] Behavior when calling IDBCursor.continue multiple
times
Cc: Eliot Graff; Jeremy Orlow; public-webapps@w3.org
Subject: RE: [indexeddb] Behavior when calling IDBCursor.continue multiple
times
I like what you wrote :-)
Israel
On Tuesday, July 12, 2011 5:18 PM, Jonas Sicking wrote:
On Tue, Jul 12, 2011 at 4:55 PM, Israel Hilerio isra
, or has iterated past its end.
Eliot
From: public-webapps-requ...@w3.org
[mailto:public-webapps-requ...@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
On Tue, Jul 12, 2011 at 4:55 PM, Israel Hilerio isra...@microsoft.com wrote:
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
I like what you wrote :-)
Israel
On Tuesday, July 12, 2011 5:18 PM, Jonas Sicking wrote:
On Tue, Jul 12, 2011 at 4:55 PM, Israel Hilerio isra...@microsoft.com wrote:
I see what you're saying.
What we originally wanted to convey was that calling this method
consecutively or in a row
] 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
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 isra...@microsoft.com wrote:
We
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 isra...@microsoft.comwrote:
We noticed that the spec doesn’t say anything about what needs to happen
if IDBCursor.continue is called multiple
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
