Did you find bugs in the Native JSON implementation?

What errors, if any, have you found in the current batch of embedded JSON implementations?

FYI - this should be some kind of central repo from the original json errors.

The reason I feel this is important is because the de facto standard json2.js does not set itself if it finds an inline implementation, so it is very important to identify inline errors so that you can decide whether to force json2 to force overwrite native if the error affects your code.

0
source share
3 answers

Chrome has a JavaScript version of JSON.stringify, not the native one, which is why it is actually slower than JS on JSON.org (although it handles more cases with edges).

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

+1

Firefox 3.6 ignores the return value of replacer in stringify.

bug report

test page

180 browser / platform combinations acknowledge error

0
source

All Articles