[w3c/IndexedDB] Clarify usage of resizable ArrayBuffer as keys (Issue #509)

ArnaudBienner created an issue (w3c/IndexedDB#509)

Using a key defined like this: `key = new ArrayBuffer(8, { maxByteLength: 16 });`
* Works in Safari
* Returns type error in Chrome
* Will return data error in Firefox once fixed (crashes currently)

See [this Firefox bug for details and a reproducer](https://bugzilla.mozilla.org/show_bug.cgi?id=2074390).

I don't see anything in the spec that forbids it, but as @asutherland [noted here](https://phabricator.services.mozilla.com/D328135#11416254), resizable arrays were added to the spec in https://github.com/tc39/ecma262/pull/3116 i.e. after `ArrayBuffer` as keys were added to the IDB spec (#21).

We don't have the concerns that we have for having SharedArrayBuffers as keys (#506).

So we need to decide whether we should forbid it explicitly. If not, we should fix Chrome and Firefox implementations.

At a first glance, I don't see any reason to prevent the use of resizable `ArrayBuffer` as keys.

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

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