Bug 71130

Summary: IndexedDB: IDB should only fire blocked event after other connections receive VersionChangeEvents
Product: WebKit Reporter: jochen
Component: WebCore Misc.Assignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: bfulgham, dgrogan, hans, jsbell, sihui_liu, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   

jochen
Reported 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)
Attachments
Radar WebKit Bug Importer
Comment 1 2022-07-11 14:50:57 PDT
Brent Fulgham
Comment 2 2022-07-11 14:51:11 PDT
We don't seem to have taken this fix into WebKit. Sihui: Should this be incorporated?
Sihui Liu
Comment 3 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 ***
Note You need to log in before you can comment on or make changes to this bug.