Comment #31 on issue 761 by erik.corry: Incorrect UTF-8 encoding/decoding for non-BMP characters in String related functions
http://code.google.com/p/v8/issues/detail?id=761
I'm going to fix the API functions in V8 that accept and produce UTF-8 so that they uinderstand surrogate pairs I'm not sure whether that will be enough to fix this issue vis a vis web sockets, because I am not sure that Chromium uses those API functions.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
