-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Realm used "When a WebSocket message has been received" #1959
Comments
Same thing for the |
I mean, we do this all over the spec, but I'll take this as an indication that this particular case is causing implementer pain and is worth fixing. |
Ms2ger is trying to implement some of this stuff in Servo and running into all sorts of underdefined cases... |
We also need to specify the realm for the MessageEvent created. That is blocked on whatwg/dom#349 and #1935 landing. In the meantime, #1964 is up for the blob and arraybuffer, but I'll leave this open until all are fixed. |
Closes #1959. All other MessageEvents are created as part of "fire an event", which is covered by whatwg/dom#352.
Closes #1959. All other MessageEvents are created as part of "fire an event", which is covered by whatwg/dom#352.
Closes #1959. All other MessageEvents are created as part of "fire an event", which is covered by whatwg/dom#352.
Closes whatwg#1959. All other MessageEvents are created as part of "fire an event", which is covered by whatwg/dom#352.
https://html.spec.whatwg.org/multipage/comms.html#feedback-from-the-protocol
… we create a
Blob
without defining the global object it should be associated with.CC @bzbarsky @annevk @domenic
The text was updated successfully, but these errors were encountered: