Bug 71130 - IndexedDB: IDB should only fire blocked event after other connections receive VersionChangeEvents
Summary: IndexedDB: IDB should only fire blocked event after other connections receive...
Status: RESOLVED DUPLICATE of bug 152593
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2011-10-28 12:03 PDT by jochen
Modified: 2022-08-01 18:59 PDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jochen 2011-10-28 12:03:10 PDT 
Currently, blocked is fired at the connection calling setVersion if there are other open connections, even if they close themselves in their VersionChangeEvent handler. (see also http://code.google.com/p/chromium/issues/detail?id=100123)
Comment 1 Radar WebKit Bug Importer 2022-07-11 14:50:57 PDT 
<rdar://problem/96844686>
Comment 2 Brent Fulgham 2022-07-11 14:51:11 PDT 
We don't seem to have taken this fix into WebKit. Sihui: Should this be incorporated?
Comment 3 Sihui Liu 2022-08-01 18:59:18 PDT 
This is our current behavior, see UniqueIDBDatabase::notifyCurrentRequestConnectionClosedOrFiredVersionChangeEvent.

*** This bug has been marked as a duplicate of bug 152593 ***