gecko-dev/testing/web-platform/meta/webmessaging
violet de4e05e120 Bug 1538622 - StructuredClone serialize and deserialize should treat back reference consistently r=jorendorff
1. If an object needs a custom function to |write|, it will be added to |memory|
   in |JSStructuredCloneWriter| before calling the custom function. But in
   JSStructuredCloneReader::startRead we did the opposite. This will cause
   out-of-order if the custom function also writes some objects (e.g.
   WriteStructuredCloneImageData). We fix this by keeping the same order in
   |startRead|.
2. |JS_WriteTypedArray| should not call |writeTypedArray| directly, because it
   will miss an entry in |memory| for the typed array itself. We fix this by calling
   |startWrite| instead.

Differential Revision: https://phabricator.services.mozilla.com/D24670

--HG--
extra : moz-landing-system : lando
2019-03-29 00:42:08 +00:00
..
message-channels Bug 1502802 - Implement PostMessageOptions for MessagePort, r=smaug 2018-10-29 16:26:30 +01:00
with-ports Bug 1502802 - Implement PostMessageOptions for Window, r=smaug 2018-10-29 16:26:30 +01:00
without-ports Bug 1538622 - StructuredClone serialize and deserialize should treat back reference consistently r=jorendorff 2019-03-29 00:42:08 +00:00
worker_postMessage_user_activation.tentative.html.ini