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.

Sign up for GitHub

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

Jump to bottom

Consider throwing for postMessage() on a detached MessagePort #4265

Open
annevk opened this issue Jan 2, 2019 · 0 comments
Open

Consider throwing for postMessage() on a detached MessagePort #4265

annevk opened this issue Jan 2, 2019 · 0 comments
Labels
addition/proposal New features or enhancements topic: serialize and transfer

Comments

@annevk
Copy link
Member

annevk commented Jan 2, 2019

As proposed by @mkruisselbrink in #4210 (comment) and seconded by @bakulf. Web compatibility unknown.

As currently specified this change wouldn't necessarily affect DedicatedWorkerGlobalScope as it doesn't close its port when close() is invoked on the worker. Should it?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
addition/proposal New features or enhancements topic: serialize and transfer
Milestone
No milestone
Development

No branches or pull requests
1 participant
@annevk