[Bug 17681] [IndexedDB] Operations that raise multiple exceptions types should define order

• From: <bugzilla@jessica.w3.org>
• Date: Thu, 07 Feb 2013 21:32:37 +0000
• To: public-webapps@w3.org
• Message-ID: <bug-17681-2927-YbbSHBxNKI@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17681

Eliot Graff <eliotgra@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |eliotgra@microsoft.com
         Resolution|---                         |FIXED

--- Comment #4 from Eliot Graff <eliotgra@microsoft.com> ---
Made the following additions to method descriptions:

IDBDatabase.transaction() & IDBDatabaseSync.transaction()
If the value for the mode parameter is invalid, this method MUST throw a
JavaScript TypeError exception.

IDBObjectStore.openCursor() & IDBObjectStoreSync.openCursor()
If the value for the direction parameter is invalid, this method MUST throw a
JavaScript TypeError exception.

IDBIndex.openCursor() & IDBIndexSync.openCursor()
If the value for the direction parameter is invalid, this method MUST throw a
JavaScript TypeError exception.

IDBIndex.openKeyCursor() & IDBIndexSync.openKeyCursor()
If the value for the direction parameter is invalid, this method MUST throw a
JavaScript TypeError exception.

IDBCursor.advance() & IDBCursorSync.advance()
Nothing added. This already existed:
If the value for count is 0 (zero) or a negative number, this method MUST throw
a JavaScript TypeError exception.

IDBFactory.open() & IDBFactorySync.open()
If the value of version is 0 (zero) or a negative number, this method MUST
throw a JavaScript TypeError exception.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 7 February 2013 21:32:38 UTC