On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters sim...@opera.com wrote:
http://www.w3c-test.org/websockets/keeping-connection-open/001.html --
the test is wrong. Passing undefined means the argument is not present
per Web IDL, so this should not throw.
I assume you mean some other test
On Thu, 26 Mar 2015 18:24:22 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/26/15 10:51 AM, Arthur Barstow wrote:
If anyone is willing to help with the failure analysis, that would be
very much appreciated.
Taking a brief look at some of the failures in Firefox, in addition to
the ones
On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters sim...@opera.com wrote:
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.
(Will have a look.)
On 4/2/15 8:15 AM, Simon Pieters wrote:
http://www.w3c-test.org/websockets/keeping-connection-open/001.html --
the test is wrong. Passing undefined means the argument is not
present per Web IDL, so this should not throw.
I assume you mean some other test since that test doesn't use undefined.
On Thu, 26 Mar 2015 18:06:15 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/26/15 1:02 PM, Boris Zbarsky wrote:
It looks like the tests that are failed with an Error as opposed to a
Fail are not being counted in the 2 passes list?
And the for
On Thu, 26 Mar 2015 16:37:28 +0100, Olli Pettay o...@pettay.fi wrote:
websockets/interfaces.html the test itself has bugs (uses old
idlharness.js?).
https://github.com/w3c/web-platform-tests/pull/1714
--
Simon Pieters
Opera Software
On Thu, 26 Mar 2015 16:37:28 +0100, Olli Pettay o...@pettay.fi wrote:
Also 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.
It probably matched the spec at the time the test was
On 3/26/15 10:51 AM, Arthur Barstow wrote:
If anyone is willing to help with the failure analysis, that would be
very much appreciated.
Taking a brief look at some of the failures in Firefox, in addition to
the ones Olli already posted about:
On 26/03/15 15:37, Olli Pettay wrote:
websockets/interfaces.html the test itself has bugs (uses old
idlharness.js?).
Also 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.
If
On 3/26/15 10:51 AM, Arthur Barstow wrote:
* All results http://w3c.github.io/test-results/websockets/all.html
* 2 passes http://w3c.github.io/test-results/websockets/less-than-2.html
Overall these results are pretty good: 97% of the 495 tests have two or
more passes.
Arthur,
It looks like
On 3/26/15 1:02 PM, Boris Zbarsky wrote:
It looks like the tests that are failed with an Error as opposed to a
Fail are not being counted in the 2 passes list?
And the for
http://www.w3c-test.org/websockets/keeping-connection-open/001.html
which is all-Timeout.
-Boris
Earlier today I ran the Web Sockets tests on Chrome 41, Chrome/Canary
43, FF Nightly 39, IE 11, and Opera 12 and pushed the results to the
test-results repo:
* All results http://w3c.github.io/test-results/websockets/all.html
* 2 passes
On 03/26/2015 04:51 PM, Arthur Barstow wrote:
Earlier today I ran the Web Sockets tests on Chrome 41, Chrome/Canary 43, FF
Nightly 39, IE 11, and Opera 12 and pushed the results to the
test-results repo:
* All results http://w3c.github.io/test-results/websockets/all.html
* 2 passes
13 matches
Mail list logo
