28566 2015-04-27 09:51:01 +0000 Add a synchronous structured clone API 2016-03-03 17:33:10 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED https://html.spec.whatwg.org/#structured-clone P3 normal Unsorted 1 contributor ian annevk ian mike travil contributor oldest_to_newest 119931 0 contributor 2015-04-27 09:51:01 +0000 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 119932 1 annevk 2015-04-27 09:51:44 +0000 See https://lists.w3.org/Archives/Public/public-webapps/2015AprJun/thread.html#msg251 for context and general support to add this. 119958 2 travil 2015-04-27 19:47:27 +0000 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). 120105 3 ian 2015-05-05 21:38:40 +0000 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. 125343 4 annevk 2016-03-03 17:33:10 +0000 https://github.com/whatwg/html/issues/793