W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 25 Aug 2010 14:50:47 +0000
To: public-webapps@w3.org
Message-ID: <bug-10430-2927@http.www.w3.org/Bugs/Public/>
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: andreip@google.com
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@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.
Received on Wednesday, 25 August 2010 14:50:48 GMT

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