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

websockets/interfaces/WebSocket/events/013.html is buggy #1691

Open
AFBarstow opened this issue Mar 30, 2015 · 2 comments
Open

websockets/interfaces/WebSocket/events/013.html is buggy #1691

AFBarstow opened this issue Mar 30, 2015 · 2 comments
Labels
html websockets

Comments

@AFBarstow
Copy link
Contributor

Olli Pettay reported an issue with websockets/interfaces/WebSocket/events/013.html

[[
https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0894.html

websockets/interfaces/WebSocket/events/013.html is buggy. Seems to rely on blink/presto's EventHandler behavior, which is not what the specs says should happen.
]]

/Cc @SmauG [anyone know know Olli's github handle?]
@foolip
Copy link
Member

foolip commented Apr 13, 2018

This issue is 3 years old. https://wpt.fyi/websockets/interfaces/WebSocket/events/013.html broken because of #10457 so can't investigate.

Olli is @smaug----

@foolip
Copy link
Member

foolip commented Apr 13, 2018

Just looking at the code and OP, think this was about {handleEvent:this.unreached_func("handleEvent was called")} as the event handler, which is a silly thing which is actually spec'd and (I think) interoperable now. So once #10457 is fixed this issue can be closed if the tests are passing in all browsers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
html websockets
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@foolip @AFBarstow @marcoscaceres