[Webkit-unassigned] [Bug 30384] Please consider escaping non-ASCII characters for JSON
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 15 14:41:47 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=30384
Alexey Proskuryakov <ap at webkit.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS/Version|Windows XP |All
Summary|wrong unicode map or buggy |Please consider escaping
|JSON.stringify method |non-ASCII characters for
| |JSON
Platform|PC |All
CC| |oliver at apple.com
--- Comment #3 from Alexey Proskuryakov <ap at webkit.org> 2009-10-15 14:41:48 PDT ---
Safari converts all text sent to server to NFC normalization form, see
<http://www.unicode.org/faq/normalization.html>. This is intentional - some
servers cannot cope with data in other normalization forms, which is common on
Mac OS X.
For text strings, this should be completely transparent - conversion to NFC
basically combines accents and replaces deprecated characters with their modern
equivalents. According to the Unicode specification, a compliant implementation
can make no difference between Unicode normalization forms, so any server that
is sensitive to this Safari behavior is itself non-compliant.
CC'ing Oliver to consider escaping non-ASCII characters. I'm rather skeptical
about this idea - JS code can always perform the escaping itself, after
stringify() but before send(). Otherwise, this is a duplicate of bug 30387.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list