-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
worker.onmessage is not called #26856
Comments
Thanks, we should also consider supporting |
Refs: #34057 |
To be clear, #34057 does this for |
Yep, not really seeing much value in having |
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document. |
If you run the
main.mjs
file above, you’ll see only the EventEmitter handler is called, but not the one registered viaonmessage
.I think for consistence (as well as the fake MessageEvent handling introduced in #26082), it is desirable to add support for
onmessage
onWorker
.cc @addaleax
The text was updated successfully, but these errors were encountered: