Closed Bug 1288298 Opened 7 years ago Closed 6 years ago
Fix Unicode encoding mismatch between JS-Plugins and the PPAPI Plug-in
There is a dedicated Web API: https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder But there is another one for the lazy bones, which encodes the JS string into the old and fake "binary string": var bin_str = unescape(encodeURI(str));
We do use TextEncoder API in jsplugin, but as I know this bug will dig into Python and C++ generator code to make sure encoding in lower layer's works well.
... but maybe jsplugin need to be modified too. Thanks for the info. :)
> - A new class (i.e. |UnicodeString|) and a new modifier (i.e. > |UnicodeEncoding|) to handle transcoding between UTF-8 encoded strings and > printable-characters-only JSON strings. s/modifier/manipulator
Comment on attachment 8794098 [details] [review] https://github.com/mozilla/flapper.js/pull/62 According to the discussion offline, we would do transcoding stuffs in Gecko instead of doing that in RPC. If we really encounter performance issues, we would breakdown the issues and have further studies by then.
Un-assign myself because this bug would be handled by Peter's patch.
Assignee: brsun → nobody
Can't reproduce this issue anymore.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.