16465 2012-03-21 15:33:34 +0000 [IndexedDB] Error handling of db.transaction('mystore', 'some invalid value here') should be defined 2012-05-02 21:26:57 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified All All RESOLVED FIXED P2 normal --- 1 odinho dave.null jonas mike public-webapps public-webapps-bugzilla oldest_to_newest 65898 0 odinho 2012-03-21 15:33:34 +0000 Right now it isn't defined what happens if you don't input "readonly" or "readwrite". "versionchange" also exist, -- but it's not valid for transaction(), but it needs to be defined in some way. Also, I guess it'd be interesting to get the same for openCursor etc. as well. What is done now? Throwing InvalidStateError? Ignoring and doing default "readonly"? 65908 1 jonas 2012-03-21 19:36:15 +0000 (In reply to comment #0) > Right now it isn't defined what happens if you don't input "readonly" or > "readwrite". If you look at the source code of the spec this is actually defined to throw a TypeError. However somewhere along the way it appears that ReSpec has changed and is no longer displaying the "exceptions". This means that there are whole swaths of the spec that is now ambiguous. We need to fix this asap. I'll start a thread on the list. > "versionchange" also exist, -- but it's not valid for transaction(), but it > needs to be defined in some way. Indeed. This needs to be fixed. > Also, I guess it'd be interesting to get the same for openCursor etc. as well. Same thing here. This is actually defined in the spec source, but ReSpec isn't showing it any more. 67262 2 jonas 2012-05-02 21:26:57 +0000 This is defined now that we have fixed the respec issue.