Comment #24 on issue 761 by [email protected]: Incorrect UTF-8
encoding/decoding for non-BMP characters in String related functions
http://code.google.com/p/v8/issues/detail?id=761
Hi yutak
We are using older chromium 11.01 with websocket protocol version 0 support
and issue very much exist in that.
We have support for websocket protocol version 10 in native server and
tried with chrome version 14 (14.0.835.186) and same issue exist.
But dev version 15 (15.0.874.21) of chrome works fine and we are able to
receive properly all characters including non BMP. Please note that we are
sending all data utf8 encoded in text frames.
I don't know whether we need to file a bug for chrome versions < 15
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
