New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

issue 651572

Sign in to add a comment

Issue 651773: Many failing web-platform-tests for Web Sockets that pass in Firefox and Edge

Reported by, Sep 30 2016 Project Member

Issue description

These failures need analysis, but may point to low-hanging fruit for improving interop. Judgement is required, the failures may be entangled with spec issues.

See  issue 651572  for the source of this data, which includes failing subtests.

Note: Results may have changed in the interim.

Comment 1 by, Oct 3 2016

I took a very brief look. Many tests are failing with

assert_equals: wasClean should be true expected true but got false

This is happening on a normal browser-initiated close, so we shouldn't be failing. Either we have some bug that is triggered by the web-platform-tests but not by our layout tests, or there's something odd going on with the test harness.

There are some tests with different issues that might be easier to fix, eg. websockets/constructor/002.html.

Comment 2 by, Dec 15 2016

ricea@, since you've taken a look and agree there are some things worth looking into here, should we perhaps mark this as 'Available' with an appropriate priority to get it off the "untriaged" Hotlist-Interop list?  Blink>Network has a long tail of untriaged bugs :-(

Comment 3 by, Dec 16 2016

Status: Available (was: Untriaged)

Comment 4 by, Dec 11 2017

I fixed up some w-p-t WebSocket tests recently: Unfortunately, there are many broken tests and we cannot justify resources to fix them. The good news is, in many cases the browsers were interoperable and only the tests were wrong.

This issue is very nearly "WontFix" but if some kind person fixes the tests then we can take another look.

Comment 5 by, Dec 12 2017

Status: WontFix (was: Available)
WontFixing then, I think the right approach here would be for those incorrect tests to show up in a triage in upstream web-platform-tests, using up-to-date results from all browsers on

Sign in to add a comment