- From: <bugzilla@jessica.w3.org>
- Date: Tue, 23 Nov 2010 03:32:21 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11385 Summary: Bring the sync APIs back in sync with the async ones Product: WebAppsWG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Indexed Database API AssignedTo: dave.null@w3.org ReportedBy: pablo.castro@microsoft.com QAContact: member-webapi-cvs@w3.org CC: mike@w3.org, public-webapps@w3.org We've been maintaining the async API as the reference one and there are a few things that the sync API is now out of sync on. This bug is to track bringing them back together (and hopefully we'll keep them in sync going foward). Differences as of 11/22/10: 1. Remove the IDBDatabaseSync.description attribute 2. IDBDatabaseSync.close method needs to be added 3. IDBDatabaseSync.deleteObjectStore: need to add the exception for the case of NOT_ALLOWED_ERR (outside of setVersion) 4. Remove the IDBDatabaseSync.openObjectStore method 5. IDBDatabaseSync.transaction is missing the "mode" parameter 6. Remove IDBObjectStoreSync.mode and the realted READ_ONLY and READ_WRITE constants 7. IDBIndexSync.get: allow range objects as keys where we return the first element of the range 8. IDBTransactionSync needs the READ_WRITE, READ_ONLY and VERSION_CHANGE constants, and the "mode" attribute 9. IDBTransactionSync.static needs to be removed 10. most sync methods need to get their errors table updated from the async counterparts (in particular TRANSACTION_INACTIVE_ERR and many DATA_ERR cases aren't covered) 11. most (all?) sync samples need updating to reflect the changes to the sync API Spec changes to follow soon. -- 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 Tuesday, 23 November 2010 03:32:27 UTC