This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/multipage/infrastructure.html Multipage: https://html.spec.whatwg.org/multipage/#structured-clone Complete: https://html.spec.whatwg.org/#structured-clone Referrer: https://html.spec.whatwg.org/multipage/ Comment: Add a synchronous structured clone API Posted from: 77.57.114.240 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:40.0) Gecko/20100101 Firefox/40.0
See https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/thread.html#msg251 for context and general support to add this.
I think this is interesting, but isn't the use case in general for cross-origin? And in order to get your Transfer-Blob to a cross-origin destination, you probably have to use an existing gateway like postMessage, which is already going to use structured clone internally? And if the use case is for object graph serialization/rehydration, then I would like to see this proceed in EcmaScript. I noticed Object.assign which is a "shallow" object clone. A "deep" clone would also be nice and could use structured clone (though it would be nice to keep prototype connections if possible).
I don't understand the use case here. In any case this probably belongs in the JS spec. I don't think HTML should be where we maintain the core concept of structured cloning.
https://github.com/whatwg/html/issues/793