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.

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

websockets/interfaces/WebSocket/readyState/003.html -- bugy? #1695

Open
AFBarstow opened this issue Mar 30, 2015 · 1 comment
Open

websockets/interfaces/WebSocket/readyState/003.html -- bugy? #1695

AFBarstow opened this issue Mar 30, 2015 · 1 comment

Comments

@AFBarstow
Copy link
Contributor

Boris reported this:

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

http://www.w3c-test.org/websockets/interfaces/WebSocket/readyState/003.html looks wrong to me: the value it should get is in fact undefined, since the property got deleted from the prototype.
]]

/Cc @bzbarsky

@foolip
Copy link
Member

foolip commented Apr 13, 2018

This issue has been open for 3 years :)

Current results:
https://wpt.fyi/websockets/interfaces/WebSocket/readyState/003.html
https://wpt.fyi/websockets/interfaces/WebSocket/readyState/003.html?wss

I get the same error with wpt run locally, but not at http://w3c-test.org/websockets/interfaces/WebSocket/readyState/003.html...

In Chrome devtools I see "Failed to load resource: the server responded with a status of 500 (Internal Server Error)" so something pretty odd is happening here.

Will file a separate issue for that, when fixed perhaps this issue can be reproduced again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants