Re: [w3c/IndexedDB] Clarify the handling of +0 and -0 in keys (Issue #375) from Andrew Sutherland on 2022-01-26 (public-webapps-github@w3.org from January 2022)

From: Andrew Sutherland <notifications@github.com>
Date: Tue, 25 Jan 2022 18:50:11 -0800
To: w3c/IndexedDB <IndexedDB@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/IndexedDB/issues/375/1021811838@github.com>

Thanks so much for the spec bug and Firefox bug with easy reproduction!  Firefox was not intentionally normalizing here, bit manipulations just went wrong when trying to create a binary encoding that sorted sensibly.

That said, normalizing to +0 intentionally does seem desirable because of the uniqueness problem (because of the language around key [equal to](https://w3c.github.io/IndexedDB/#equal-to)).

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

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

Received on Wednesday, 26 January 2022 02:50:23 UTC