- From: Rızgar Ozan <notifications@github.com>
- Date: Tue, 15 Sep 2026 10:11:35 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 15 September 2026 17:11:39 UTC
RizgarOzan created an issue (w3c/IndexedDB#507)
The "For web developers" box for `deleteDatabase()` says:
> If the request is successful request's result will be null.
But the `deleteDatabase(name)` method steps set it to undefined:
> Otherwise, set request's result to undefined, set request's done flag to true, and fire a version change event named success ...
The steps have said undefined since #202 (2017), and that's what engines return: in Chromium (Edge 153), `indexedDB.deleteDatabase("x")` fires `success` with `request.result === undefined`. WebKit and Gecko also leave the result undefined on success.
Suggested fix: change "will be null" to "will be undefined" in the domintro box.
Came up in mdn/content#45719, which fixes the same thing on MDN's `deleteDatabase()` page.
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/507
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/IndexedDB/issues/507@github.com>
Received on Tuesday, 15 September 2026 17:11:39 UTC