Re: [w3c/IndexedDB] Clarify interaction of IndexedDB lifecycles with relation to document and worker lifecycle mechanics (Issue #416)

After the [update to the WPT](https://github.com/web-platform-tests/wpt/commit/1849930aff8c8fb16ad56e280ceff2292688a89c), Blink is [failing the test](https://crbug.com/331539884). This is because Blink does not dispatch any events after the iframe is detached, so the test hangs waiting for an error event. At least that is part of it. IDB would also need to explicitly send an error event in this case, it's just that doing so currently has no effect due to that other behavior of Blink, which is implemented at a fairly [core level](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/dom/events/event_target.cc;l=915-920;drc=2a5aaed0ff3a0895c8551495c2656ed49baf742c) (i.e. changing this would have widespread effects beyond IDB).

Perhaps related: https://github.com/whatwg/html/issues/10194 - @domfarolino any insights?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/416#issuecomment-2050713160
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/416/2050713160@github.com>