Actually, what's the use case for readyState? I can't think of any uses that we'd want to encourage. Maybe we should just remove it.
J On Wed, Aug 25, 2010 at 3:50 PM, <bugzi...@jessica.w3.org> wrote: > http://www.w3.org/Bugs/Public/show_bug.cgi?id=10430 > > Summary: [IndexedDB] We need to make it more clear IDBRequests > can be reused and spec readyState's behavior > Product: WebAppsWG > Version: unspecified > Platform: PC > OS/Version: All > Status: NEW > Severity: normal > Priority: P2 > Component: Indexed Database API > AssignedTo: andr...@google.com > ReportedBy: jor...@chromium.org > QAContact: member-webapi-...@w3.org > CC: m...@w3.org, public-webapps@w3.org > > > http://www.w3.org/TR/IndexedDB/#idl-def-IDBRequest right now clearly > assumes > IDBRequests are only going to be used once. But IDBCursor.continue() > reuses > them. At the very least, we'll need to clean up the .readyState section to > make it clear it's possible to go from DONE to LOADING (or we can remove it > altogether?). I think some notes explicitly pointing out that some parts > of > the API reuse them would be helpful as well. > > -- > Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > >