19878 2012-11-06 12:41:52 +0000 Revert change in Close-reason-unpaired-surrogates.htm ? 2014-01-17 14:22:38 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Test suite unspecified PC All RESOLVED MOVED P2 normal --- 1 zcorpan dave.null art.barstow krisk mike public-webapps public-webapps-bugzilla oldest_to_newest 77941 0 zcorpan 2012-11-06 12:41:52 +0000 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? 77960 1 krisk 2012-11-06 17:38:04 +0000 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 77971 2 zcorpan 2012-11-06 19:15:28 +0000 Those tests don't seem to run. The websocket.js file is missing. 77972 3 zcorpan 2012-11-06 19:19:08 +0000 They also don't seem to test an unpaired surrogate in the reason (which is what was removed here). 97972 4 art.barstow 2014-01-03 17:38:49 +0000 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 ;-). 98071 5 zcorpan 2014-01-07 13:46:31 +0000 Yes, comment 0 still applies AFAICT. 98712 6 art.barstow 2014-01-17 14:22:38 +0000 This bug has been moved to Github w-p-t as as Issue 522 <https://github.com/w3c/web-platform-tests/issues/522>