-
Notifications
You must be signed in to change notification settings - Fork 315
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
messageerror event should use ExtendableMessageEvent #1193
Comments
Agreed! |
For the first place this sentence occurs (where the actual message uses ExtendableMessageEvent) definitely. For Client.postMessage using MessageEvent is correct (and consistent with the rest of the algorithm) of course. |
Is the event really intended to be extendable? If not, perhaps adding Client to the enum at https://html.spec.whatwg.org/multipage/comms.html#the-messageevent-interfaces would be a better choice. |
I think it'd make sense to allow lifetime extensions to messageerror events. Otherwise, we can't guarantee that the event handlers will run to completion. |
Spec says:
but MessageEvent.source cannot contain the source if it is a Client. We should probably use ExtendableMessageEvent instead.
The text was updated successfully, but these errors were encountered: