71130 2011-10-28 12:03:10 -0700 IndexedDB: IDB should only fire blocked event after other connections receive VersionChangeEvents 2022-08-01 18:59:18 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) All All RESOLVED DUPLICATE 152593 InRadar P2 Normal --- 1 jochen webkit-unassigned bfulgham dgrogan hans jsbell sihui_liu webkit-bug-importer oldest_to_newest 492578 0 jochen 2011-10-28 12:03:10 -0700 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) 1882137 1 webkit-bug-importer 2022-07-11 14:50:57 -0700 <rdar://problem/96844686> 1882138 2 bfulgham 2022-07-11 14:51:11 -0700 We don't seem to have taken this fix into WebKit. Sihui: Should this be incorporated? 1888281 3 sihui_liu 2022-08-01 18:59:18 -0700 This is our current behavior, see UniqueIDBDatabase::notifyCurrentRequestConnectionClosedOrFiredVersionChangeEvent. *** This bug has been marked as a duplicate of bug 152593 ***