parseJSON Chrome

Reported by:	debug@quomodo.com	Owned by:	debug@quomodo.com
Priority:	undecided	Milestone:	1.next
Component:	ajax	Version:	1.5.1
Keywords:		Cc:
Blocked by:		Blocking:

Description

Hello,

On Chrome, window.JSON.parse fails for:

'{a:"x[TAB]y"}' where [TAB] is the ASCII character 9

The jQuery parseJSON has the comment:

// Try to use the native JSON parser first

but it does not try, it just tests if window.JSON.parse is available.

Why not try, and when it fails try the alternate (new Function("return " + data))() ?

Vianney Hully

Attachments (0)

Change History (4)

Changed April 08, 2011 01:55PM UTC by addyosmani comment:1

owner:	→ debug@quomodo.com
status:	new → pending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsFiddle.net that reproduces the issue experienced to help us assess your ticket!

Additionally, test against the jQuery (edge) version to ensure the issue still exists.

Changed April 15, 2011 04:57AM UTC by timmywil comment:2

component:	unfiled → ajax

Changed April 29, 2011 07:55AM UTC by trac-o-bot comment:3

resolution:	→ invalid
status:	pending → closed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Changed April 29, 2011 09:32AM UTC by debug@quomodo.com comment:4

In the last Chrome version - 11.0.696.57 -, the JSON.parse is fixed so both $.parseJSON( '{"a":"x y"}' ) and JSON.parse( {"a":"x y"}' ) work fine.

The ticket can be closed.

Side navigation