Bug 1774866 Comment 26 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Support for structured cloning of native types in FF104 ([Bugzilla #1556604](https://bugzilla.mozilla.org/show_bug.cgi?id=1556604#c33) "Allow structured cloning of native error types") was added for serializing stack in `window.postMessage()` and `structureCloned()`. This resulted in addition of compatibility notes as shown here: https://github.com/mdn/browser-compat-data/pull/17008

[Comment 19 above](https://bugzilla.mozilla.org/show_bug.cgi?id=1774866#c19) says:

> We are going to add stack cloning support to other APIs like worker's postMessage.

1. Can you confirm that this was what is delivered by this bug fix? Anything else?
2. If so, would this represent "full spec compliance"? I.e. do we look like partial support before now and full support in FF110 
   - If not, then I can add the change as a note in browser compatibility data. If not, then perhaps need to mark the current releases as partial implementation and the FF110 as first full implementation.
Support for structured cloning of native types in FF104 ([Bugzilla #1556604](https://bugzilla.mozilla.org/show_bug.cgi?id=1556604#c33) "Allow structured cloning of native error types") was added for serializing stack in `window.postMessage()` and `structuredCloned()`. This resulted in addition of compatibility notes as shown here: https://github.com/mdn/browser-compat-data/pull/17008

[Comment 19 above](https://bugzilla.mozilla.org/show_bug.cgi?id=1774866#c19) says:

> We are going to add stack cloning support to other APIs like worker's postMessage.

1. Can you confirm that this was what is delivered by this bug fix? Anything else?
2. If so, would this represent "full spec compliance"? I.e. do we look like partial support before now and full support in FF110 
   - If not, then I can add the change as a note in browser compatibility data. If not, then perhaps need to mark the current releases as partial implementation and the FF110 as first full implementation.
Support for structured cloning of native types in FF104 ([Bugzilla #1556604](https://bugzilla.mozilla.org/show_bug.cgi?id=1556604#c33) "Allow structured cloning of native error types") was added for serializing stack in `window.postMessage()` and `structuredCloned()`. This resulted in addition of compatibility notes as shown here: https://github.com/mdn/browser-compat-data/pull/17008

[Comment 19 above](https://bugzilla.mozilla.org/show_bug.cgi?id=1774866#c19) says:

> We are going to add stack cloning support to other APIs like worker's postMessage.

1. Can you confirm that this was what is delivered by this bug fix? Anything else?
2. My assumption is that this can just be added as another note to the compatibility data like the ones in the issue linked above (i.e. it is not that the implementation was partially spec compliant and is fully compliant now - since the spec just says "serialize interesting data").

Back to Bug 1774866 Comment 26