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 11389 - IDBTransaction.READ_ONLY should probably be 0
Summary: IDBTransaction.READ_ONLY should probably be 0
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Indexed Database API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Jeremy Orlow
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-23 12:29 UTC by Jeremy Orlow
Modified: 2010-12-10 14:23 UTC (History)
2 users (show)

See Also:

Attachments

Description Jeremy Orlow 2010-11-23 12:29:12 UTC 
IDBTransaction.READ_ONLY should probably be 0 rather than 1.  READ_WRITE (which is currently 0) used to be the default, but it no longer is.  Often with enums like this, the 0th item is the default so it probably makes sense to switch the two.
Comment 1 Jeremy Orlow 2010-12-10 14:23:32 UTC 
changeset:   98:c9ddfc1efda4
tag:         tip
user:        Jeremy Orlow <jorlow@google.com>
date:        Fri Dec 10 14:22:37 2010 +0000
summary:     Switch READ_ONLY and READ_WRITE so that READ_ONLY is 0 since it's the default for transaction().