Re: [Bug 10430] New: [IndexedDB] We need to make it more clear IDBRequests can be reused and spec readyState's behavior

On Thu, Aug 26, 2010 at 2:15 AM, Jeremy Orlow <jorlow@chromium.org> wrote:
> I asked whether LOADING should be 0 rather than 1.  (There is no 0 constant
> since we removed INITIAL.)

I agree with this.

> I also asked " is it possible to get the IDBRequest object from within the
> openCursor/continue events without saving it off somewhere?  If not, it
> probably should be."

I don't really feel strongly either way. I wouldn't be opposed to
adding a .request property to IDBCursor.

/ Jonas

> On Thu, Aug 26, 2010 at 2:46 AM, Jonas Sicking <jonas@sicking.cc> wrote:
>>
>> On Wed, Aug 25, 2010 at 3:42 PM, Jeremy Orlow <jorlow@chromium.org> wrote:
>> > On Wed, Aug 25, 2010 at 9:29 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>> >>
>> >> On Wed, Aug 25, 2010 at 8:12 AM, Jeremy Orlow <jorlow@chromium.org>
>> >> wrote:
>> >> > Also, the constants for the ready state should start with 0, not 1.
>> >> > Also, what happens if someone does the following:
>> >> > request = objectStore.openCursor();
>> >> > request.onsuccess(function() {
>> >> >     event.result.continue();
>> >> >     request.abort();
>> >> >     event.result.continue();
>> >> > }
>> >> > Also, is it possible to get the IDBRequest object from within the
>> >> > openCursor/continue events without saving it off somewhere?  If not,
>> >> > it
>> >> > probably should be.
>> >>
>> >> Didn't we decide to remove IDBRequest.abort()?
>> >
>> > Oh yeah...we did.  :-)
>> > Will file a bug.
>> > What about the other questions?
>>
>> Yes, I think we should make it clear that readyState can go from DONE
>> to LOADING.
>>
>> All other questions seemed related to abort()?
>>
>> / Jonas
>
>

Received on Thursday, 26 August 2010 17:34:10 UTC