[DJSON-9] Always escape U+2028 and U+2029 to be nice to broken JSON parsers Created: 28/Apr/13 Updated: 10/Jan/14 Resolved: 02/Aug/13
U+2028 and U+2029 should be treated like \n and, viz, escaped even when *escape-unicode* is false.
A number of JSON parsers (such as ExtJS's) think they can eval JSON in a JS runtime to decode it. This is not true, since JS does not allow U+2028 and U+2029 unescaped in strings:
While this is broken behavior, it is also quite common, so escaping these characters uniformly may ease some developer pain and surprise.
|Comment by Tim McCormack [ 28/Apr/13 9:46 PM ]|
|Comment by Stuart Sierra [ 02/Aug/13 3:25 PM ]|
Reimplemented as an additional optional argument on master.
|Comment by Stuart Sierra [ 10/Jan/14 11:10 AM ]|
Marking old issues as 'closed'