Have you found any bugs in Native JSON implementat

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 7 years ago.

What bugs, if any, have you found in the current batch of native JSON implementations?

FYI - this is meant to be a sort of central repo of native json bugs.

The reason I feel this is important is that the de-facto standard, json2.js, does not install itself if it finds a native implementation, so it is crucial to identify native bugs so that you can decide whether to force json2 to overwrite native if a bug affects your code.

Answer 1

IE8 native JSON.parse bug causes stack overflow

Answer 2

Chrome has a JavaScript implementation of JSON.stringify, instead of a native one, so it's actually slower than the JS one on JSON.org (although handles more edge cases).

http://code.google.com/p/chromium/issues/detail?id=22718

Answer 3

Firefox 3.6 ignores the replacer return value in stringify.

bug report

test page

180 browser/platform combinations confirm bug