- From: ArnaudBienner <notifications@github.com>
- Date: Mon, 25 May 2026 05:44:49 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/IndexedDB/issues/497@github.com>
ArnaudBienner created an issue (w3c/IndexedDB#497) In [Creating a request to retrieve multiple items](https://w3c.github.io/IndexedDB/#create-request-to-retrieve-multiple-items) at step 8 there is the following: 8. If running [is a potentially valid key range](https://w3c.github.io/IndexedDB/#is-a-potentially-valid-key-range) with queryOrOptions is true, then: 1. Set range to the result of [converting a value to a key range](https://w3c.github.io/IndexedDB/#convert-a-value-to-a-key-range) with queryOrOptions. Rethrow any exceptions. Since ["is a potentially valid key range"](https://w3c.github.io/IndexedDB/#is-a-potentially-valid-key-range) calls [converting a value to a key](https://w3c.github.io/IndexedDB/#convert-a-value-to-a-key) too (at step 2), we have the same call twice. In Firefox's implementation, we optimized that by having only one call to "converting a value to a key". Since this is not observable, maybe it's not worth to change the spec to make this optimization explicit, as it makes it more complex and harder to read. But if you think otherwise, I'll think about how to change it to make it explicit. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/IndexedDB/issues/497 You are receiving this because you are subscribed to this thread. Message ID: <w3c/IndexedDB/issues/497@github.com>
Received on Monday, 25 May 2026 12:44:52 UTC