Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: MessagePort closing unexpectedly with non-cloneable objects #42582

Conversation

trop[bot]
Copy link
Contributor

@trop trop bot commented Jun 19, 2024

Backport of #42535

See that PR for details.

Notes: Fixed an issue where MessagePorts could close unexpectedly with non-cloneable objects sent via postMessage.

trop bot and others added 2 commits June 19, 2024 09:27
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
@trop trop bot requested review from codebytere and a team June 19, 2024 09:27
@trop trop bot added 30-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes labels Jun 19, 2024
@jkleinsc jkleinsc merged commit 91de7d0 into 30-x-y Jun 19, 2024
20 checks passed
@jkleinsc jkleinsc deleted the trop/30-x-y-bp-fix-messageport-closing-unexpectedly-with-non-cloneable-objects-1718789235641 branch June 19, 2024 14:24
Copy link

release-clerk bot commented Jun 19, 2024

Release Notes Persisted

Fixed an issue where MessagePorts could close unexpectedly with non-cloneable objects sent via postMessage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
30-x-y backport This is a backport PR semver/patch backwards-compatible bug fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant