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

Why does BroadcastChannel.postMessage() throw an exception when called after close()? #3528

Closed
bakulf opened this issue Mar 3, 2018 · 3 comments
Closed

Why does BroadcastChannel.postMessage() throw an exception when called after close()? #3528

bakulf opened this issue Mar 3, 2018 · 3 comments
Labels
normative change topic: serialize and transfer

Comments

@bakulf
Copy link

bakulf commented Mar 3, 2018

https://html.spec.whatwg.org/multipage/web-messaging.html#security-4

In order to be consistent with other postMessage()s, probably BroadcastChannel should not throw a "InvalidStateError" DOMException.

MessagePort doesn't throw if called after being disentangled. This means that worker.postMessage() and SharedWorker.postMessage() behave at the same way.
@DANISAbbasi

This comment has been minimized.

Sign in to view
1 similar comment
@DANISAbbasi

This comment has been minimized.

Sign in to view
annevk added a commit to web-platform-tests/wpt that referenced this issue Nov 28, 2018
@annevk
BroadcastChannel: make closing return early
072ffc9 
See whatwg/html#3528.
@annevk annevk mentioned this issue Nov 28, 2018
Closed
annevk added a commit that referenced this issue Nov 28, 2018
@annevk
Make a closed BroadcastChannel return early
2e7597e 
Not throwing makes it consistent with the other postMessage() APIs.

Tests: web-platform-tests/wpt#14278.

Fixes #3528.
@annevk annevk mentioned this issue Nov 28, 2018
Closed
@annevk
Copy link
Member

annevk commented Jan 2, 2019

Wontfix in favor of #4265.

@annevk annevk closed this as completed Jan 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
normative change topic: serialize and transfer
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bakulf @annevk @DANISAbbasi