- From: Evan Stade <notifications@github.com>
- Date: Mon, 20 Oct 2025 16:39:07 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 20 October 2025 23:39:11 UTC
evanstade left a comment (w3c/IndexedDB#476) Thanks for the extra context. That is quite a long bug report. > I don't think there's any reasonable situation where application code would intentionally want to reentrantly call IDB in a case like this Agreed. > hopefully we would have uncovered any application breakage that did depend on it I think this is probably a safe bet for normal web sites, though there are situations (enterprise web apps, apps built on Electron, CEF, MS WV2...) where only some derivative of Chromium might ever be used. That means it may take more effort and time to make this update in Chromium but I think it's fine to update the spec to match FF. @SteveBeckerMSFT is the editor now, wdyt? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/476#issuecomment-3424123828 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/issues/476/3424123828@github.com>
Received on Monday, 20 October 2025 23:39:11 UTC