Re: [w3c/IndexedDB] Update for structured cloning changes in HTML (#170)

Thanks. PRs would be welcome, of course, but I'll wrangle it. :) 

The fun bit is where we currently do a clone then (1) look up properties against the clone to avoid side effects - primary key at https://w3c.github.io/IndexedDB/#dom-idbobjectstore-put and index keys at https://w3c.github.io/IndexedDB/#store-a-record-into-an-object-store which looks at the index keys, and (2) inject auto-generated keys in https://w3c.github.io/IndexedDB/#store-a-record-into-an-object-store 

I'll have to see if this can be expressed in terms of serialized records or if we will end up doing a deserialization and reserialization.


. That needs to be a serialize to _record_, deserialize _record_ to _clone_, then discard _clone_ and store _record_ on disk.

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