This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://dvcs.w3.org/hg/webapps/rev/d0ec1879951a I don't understand why this change was made. The assert seems useful for the purpose of finding impl bugs. Is it tested somewhere else? Should we revert the change?
Yes we have 4 tests that test surrogate pairs. Two of the tests test that a unpaired surrogate is 'replaced' and no longer throws and exception. http://www.w3c-test.org/webapps/WebSockets/tests/approved/Send-Unpaired-Surrogates.htm http://www.w3c-test.org/webapps/WebSockets/tests/approved/Secure-Send-unpaired-surrogates.htm http://www.w3c-test.org/webapps/WebSockets/tests/approved/Secure-Send-paired-surrogates.htm http://www.w3c-test.org/webapps/WebSockets/tests/approved/Send-paired-surrogates.htm
Those tests don't seem to run. The websocket.js file is missing.
They also don't seem to test an unpaired surrogate in the reason (which is what was removed here).
Kris, Simon - is this bug still open? According to the Draft Implementation Report, they all run <http://www.w3.org/wiki/Webapps/Interop/WebSockets> and mostly pass ;-).
Yes, comment 0 still applies AFAICT.
This bug has been moved to Github w-p-t as as Issue 522 <https://github.com/w3c/web-platform-tests/issues/522>