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
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 | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/96844686>
Brent Fulgham
We don't seem to have taken this fix into WebKit. Sihui: Should this be incorporated?
Sihui Liu
This is our current behavior, see UniqueIDBDatabase::notifyCurrentRequestConnectionClosedOrFiredVersionChangeEvent.
*** This bug has been marked as a duplicate of bug 152593 ***