Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375)

I put together a test & normalization fix for Blink. The WPT is here: 

https://chromium-review.googlesource.com/c/chromium/src/+/3700521/2/third_party/blink/web_tests/external/wpt/IndexedDB/key_negative_zero.any.js

Without a code change, as expected these are the failures:

FAIL put(v, -0) key should normalize to +0 assert_equals: key should be normalized to +0 expected 0 but got -0
FAIL put(v, +0) / getKey(v, -0) normalization assert_equals: getKey(-0) should see +0 expected 0 but got -0
FAIL put(v, -0) / getKey(v, -0) normalization assert_equals: getKey(-0) should see +0 expected 0 but got -0
FAIL put(v, -0) / getAllKeys() normalization assert_equals: key should be normalized to +0 expected 0 but got -0

Anyone want to take a look at the WPT and see if I missed any important cases? One that comes to mind is `IDBKeyRange.bound(0, 10).includes(-0)` and other permutations with open/closed bounds.


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

Message ID: <w3c/IndexedDB/issues/375/1152808831@github.com>