[Webkit-unassigned] [Bug 89379] New: IndexedDB: Implement IDBTransaction internal active flag
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jun 18 14:09:46 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=89379
Summary: IndexedDB: Implement IDBTransaction internal active
flag
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: jsbell at chromium.org
CC: dgrogan at chromium.org, jsbell at chromium.org,
alecflett at chromium.org
The IDB spec http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html says:
Transaction lifecycle:
"Transactions have an active flag, which determines if new requests can be made against the transaction."
"When a transaction is created its active flag is initially set to true." - i.e. right after the db.transaction() call
"The implementation must allow requests to be placed against the transaction whenever the active flag is true."
"Requests may be placed against a transaction only while that transaction is active. If an attempt is made to place a request against a transaction when that transaction is not active, the implementation must reject the attempt by throwing a DOMException of type TransactionInactiveError."
Version changes:
"This transaction will be active inside the onupgradeneeded event handler, allowing the creation of new object stores and indexes."
Abort:
"Otherwise this method sets the transaction's active flag to false..."
Transaction creation:
"When control is returned to the event loop, the implementation must set the active flag to false."
Firing events:
...
"Set the active flag of transaction to true."
...
"Set the active flag of transaction to false."
...
Right now we don't have a notion of non-active transaction - until it is |finished| we allow requests to be placed against it.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list