User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6; en-us) AppleWebKit/531.5 (KHTML, like Gecko) Version/4.0.3 Safari/531.7 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.3a1pre) Gecko/20090824 Minefield/3.7a1pre JSON.parse is accepting octal values, extra commas on the end of object notation, and new lines in strings all of which breaks the JSON.org spec, and that of ES5 Reproducible: Always Steps to Reproduce: 1. Search for "FAIL" in the page at http://trac.webkit.org/export/47743/trunk/LayoutTests/fast/js/JSON-parse.html Actual Results: You can find multiple failures Expected Results: lots of green :D The issue is that the JSON parser is being too lenient, just a few edge cases need to be tightened up

CC'ing brendan because i can never recall who works on JSON here :D

You remember sayrer -- or you would if you came to Ecma TC39 meetings :-P. /be

Is this something that we want to fix? Section 4 of RFC 4627 allows this tolerance as pointed out by the comment at http://mxr.mozilla.org/mozilla-central/source/dom/src/json/test/unit/test_decode.js#163

The RFC may tolerate this, but ES5 does not, and we implement the latter, not the former (except incidentally).

From the test URLs: 1. The test with this line is wrong: return jsonObject.parse("\"a\tz\""); We correctly throw an exception here (see bug 554079) - as does Chrome, but the test expects otherwise. 2. As for the test with the line: return jsonObject.parse('[1,]'); We do not throw (and therefore pass the test). Chrome throws "SyntaxError: Unexpected token" and fails the test. Need to determine the right behavior for this.

(In reply to comment #5) > From the test URLs: > > 1. The test with this line is wrong: return jsonObject.parse("\"a\tz\""); > > We correctly throw an exception here (see bug 554079) - as does Chrome, but the > test expects otherwise. This exception needs to be thrown according to es5 now, so that is a test error > > 2. As for the test with the line: return jsonObject.parse('[1,]'); > > We do not throw (and therefore pass the test). Chrome throws "SyntaxError: > Unexpected token" and fails the test. Need to determine the right behavior for > this. JSON doesn't allow additional commas in array or object literals.

At least after all the patches in my tree, the only parts of this bug that matter any more are the already-filed bug 572279 and accepting octal numbers. So I'm going to repurpose this bug to deal with octals specifically as it's the only remaining issue without a bug.

Fixed by the parser rewrite in bug 589664.