- From: Steven Becker <notifications@github.com>
- Date: Fri, 06 Jun 2025 13:15:11 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 June 2025 20:15:15 UTC
@SteveBeckerMSFT commented on this pull request. > 1. If |connection| was [=connection/closed=], return a newly [=exception/created=] "{{AbortError}}" {{DOMException}} and abort these steps. - 1. If the [=/upgrade transaction=] was aborted, run the steps Good find @stelar7! Upgrade transaction completion does [indeed reset the request's transaction to null](https://w3c.github.io/IndexedDB/#ref-for-request-transaction%E2%91%A2). The [web platform tests also verify](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/IndexedDB/upgrade-transaction-lifecycle-committed.any.js;drc=658153df0cd23ec41cb9f77e2689d342278d0ccd;l=53) this behavior. Going back to the drawing board, maybe another potential alternative involves using the request's error, which the abort sets? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/pull/458#discussion_r2132856839 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/pull/458/review/2906059956@github.com>
Received on Friday, 6 June 2025 20:15:15 UTC