Re: [w3c/IndexedDB] Spec contradicts WPT tests for detached `ArrayBuffer` passed to `getAllKeys()` (Issue #465)

SteveBeckerMSFT left a comment (w3c/IndexedDB#465)

"is a potentially valid key range" has two additional steps, which return true for "invalid value" key results, like a detached ArrayBuffer.  Because of this, I think the WPT test verifies the spec'ed behavior.

```
1. If value is a key range, return true.

2. Let key be the result of converting a value to a key with value.

3. If key is "invalid type" return false.

4. Else return true.
```

I originally defined "is a potentially valid key range" independently by duplicating parts of "convert a value to a key".  However, the final revision removed this duplication by updating "convert a value to a key" to return two different values for invalid key ranges: "invalid value" and "invalid type".  Only "invalid type" is "not a potentially valid key range".

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

Message ID: <w3c/IndexedDB/issues/465/3169028742@github.com>