This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16465 - [IndexedDB] Error handling of db.transaction('mystore', 'some invalid value here') should be defined
Summary: [IndexedDB] Error handling of db.transaction('mystore', 'some invalid value h...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-21 15:33 UTC by Odin Hørthe Omdal
Modified: 2012-05-02 21:26 UTC (History)
3 users (show)

See Also:

Attachments

Description Odin Hørthe Omdal 2012-03-21 15:33:34 UTC 
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"?
Comment 1 Jonas Sicking (Not reading bugmail) 2012-03-21 19:36:15 UTC 
(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.
Comment 2 Jonas Sicking (Not reading bugmail) 2012-05-02 21:26:57 UTC 
This is defined now that we have fixed the respec issue.