[Bug 25223] IDB exposes GC behavior
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25223 Joshua Bell jsb...@google.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |MOVED --- Comment #8 from Joshua Bell jsb...@google.com --- Moved to https://github.com/w3c/IndexedDB/issues/29 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25223] IDB exposes GC behavior
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25223 Joshua Bell jsb...@google.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|LATER |--- --- Comment #7 from Joshua Bell jsb...@google.com --- I added some blather similar to comment #3 into: https://github.com/w3c/IndexedDB/commit/bdfc9964855d0ad650ade6da3ed0dd9b43b69d6a ... but I welcome more refinement. Leaving this open until we really nail down how to describe this. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25223] IDB exposes GC behavior
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25223 Jonas Sicking jo...@sicking.cc changed: What|Removed |Added Status|NEW |RESOLVED CC||jo...@sicking.cc Resolution|--- |LATER --- Comment #4 from Jonas Sicking jo...@sicking.cc --- I agree that it's unfortunate to expose GC behavior here. But I don't see any alternative solution. The only option I could think of would be to never close databases unless the .close() function is explicitly called. It's not clear that that's web compatible at this point though. So let's not hold up the v1 spec for this at the very least. -- You are receiving this mail because: You are on the CC list for the bug.
