Always escape U+2028 and U+2029 to be nice to broken JSON parsers

Description

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:

http://timelessrepo.com/json-isnt-a-javascript-subset

While this is broken behavior, it is also quite common, so escaping these characters uniformly may ease some developer pain and surprise.

Environment

None

Attachments

0001-Escape-JS-forbidden-unicode-chars-to-be-nice-to-brok.patch

29 Apr, 2013

Activity

Stuart Sierra

January 10, 2014 at 5:10 PM

Stuart Sierra

August 2, 2013 at 9:25 PM

Tim McCormack [personal]

April 29, 2013 at 3:46 AM

Resize work item view side panel

Completed

Details

Assignee

Unassigned

Reporter

Tim McCormack [personal]

Priority

Minor

Created April 29, 2013 at 3:45 AM

Updated January 10, 2014 at 5:10 PM

Resolved January 10, 2014 at 5:10 PM