[w3c/IndexedDB] Cloning an unserializable value causes the transaction to be left inactive (Issue #490)

Zaggy1024 created an issue (w3c/IndexedDB#490)

The [clone a value](https://w3c.github.io/IndexedDB/#clone-value) steps use the `?` prefix to unwrap the serialized value, which seems to imply that any exception should immediately be returned to the caller. This prevents the transaction state being reverted back to active, so the transaction should not be usable after an exception occurs in `put()`.

Firefox, Chromium and Safari all allow a `put()` to succeed after one had thrown an exception.

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

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