tags:

views:

48

answers:

3

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.

A: 

Firefox 3.6 ignores the replacer return value in stringify.

bug report

test page

180 browser/platform combinations confirm bug

Sky Sanders
+1  A: 

http://stackoverflow.com/questions/1288962/ie8-native-json-parse-bug-causes-stack-overflow

klausbyskov
Just found that ;-)
klausbyskov
+1  A: 

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

Annie
@Annie, Nice catch. I would like to keep this question open for a while to see if it gets some love but you will get the check.
Sky Sanders