11398 2010-11-24 17:12:53 +0000 [IndexedDB] Methods that take multiple optional parameters should instead take an options object 2012-01-17 11:03:59 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified PC All RESOLVED FIXED P2 normal --- 11350 1 jorlow jorlow jonas mike odinho public-webapps public-webapps-bugzilla oldest_to_newest 42751 0 jorlow 2010-11-24 17:12:53 +0000 All methods that take multiple optional parameters (or which might possibly take multiple in the future) should be converted over to options objects like what's described in bug 11350 (for createObjectStore). 42777 1 jorlow 2010-11-25 14:50:12 +0000 My recommendation is that the following methods be converted: IDBDatabase.createObjectStore IDBObjectStore.createIndex IDBObjectStore.openCursor IDBIndex.openCursor IDBIndex.openKeyCursor IDBKeyRange.bound The following don't seem like good candidates: IDBObjectStore.put IDBObjectStore.add IDBCursor.continue This is what we're doing in Chrome anyway. 46226 2 jorlow 2011-03-03 20:50:19 +0000 Note that we decided to throw if we get an option we didn't expect. 62804 3 odinho 2012-01-17 11:03:59 +0000 Jeremy: You went back on that throwing-on-unknown, as far as I can tell from the current spec. If not I'd like to discuss why it shouldn't throw :-)