Browser-native JSON support (window.JSON)

Question

I have seen references to some browsers natively supporting JSON parsing/serialization of objects safely and efficiently via the window.JSON Object, but details are hard to come by. Can anyone point in the right direction? What are the methods this Object exposes? What browsers is it supported under?

See [When can I use JSON parsing?](http://caniuse.com/json) for info on browsers with native support for the [JSON object](http://ecma262-5.com/ELS5_Section_15.htm#Section_15.12). — outis, Dec 26 '11 at 09:38

Sasha Chedygov · Accepted Answer · 2014-05-27T01:21:00.753

112

All modern browsers support native JSON encoding/decoding (Internet Explorer 8+, Firefox 3.1+, Safari 4+, and Chrome 3+). Basically, JSON.parse(str) will parse the JSON string in str and return an object, and JSON.stringify(obj) will return the JSON representation of the object obj.

More details on the MDN article.

edited May 27 '14 at 01:21

answered May 21 '09 at 03:40

Sasha Chedygov

127,549
26
102
115

I know the support is not widespread, but using this method should be a lot faster and safer than eval()ing a string, so I want to use it where it's available. Any idea on support from other browsers? – levik May 21 '09 at 03:53
I didn't say don't use it, I said don't count on it. Definitely check to see if it's available (at this point only IE8 and the few Fx Beta users) and use it if so, but I'm just saying that you shouldn't assume the browser supports it. As of now, those two are the only browsers that support it, and WebKit is working on it right now, so it'll probably be in Google Chrome and Safari sometime soon. – Sasha Chedygov May 21 '09 at 04:00
18

Oh, and on a side note, NEVER eval() JSON strings. Instead, use one of the many JSON parsing libraries available. – Sasha Chedygov May 21 '09 at 04:08
Of the "many" libraries available, are they any preferred? Is the one at http://www.json.org/json2.js generally the most used? I noticed references to it in jQuery 1.4 source. – curthipster Feb 06 '10 at 01:20
1

@colbeerhey: Yeah, that's the one I see most often. You could also steal jQuery's. – Sasha Chedygov Feb 06 '10 at 08:03
http://code.google.com/chrome/extensions/faq.html#faq-dev-07 - Google Chrome supports natively. I don't know how long is it. – MartyIX May 02 '10 at 18:12
2

For reference, when you say "NEVER eval() ..." and then mention that json2 is the popularly supported library, it's worth noting that it does use eval, but it attempts to validate the string using regex first. This is faster than validating and parsing the string, though there are parsers that don't validate with comparable performance. json2.js is still probably the best choice, if only for its pervasiveness. – TheXenocide Nov 21 '11 at 16:40
2

@TheXenocide: Good point, but its author probably spent a good chunk of time on that validation code, so I say never `eval()` JSON strings because you will be reinventing the wheel and you will likely get it wrong. – Sasha Chedygov Nov 28 '11 at 20:00

score 30 · Answer 2 · answered Mar 12 '12 at 01:38

jQuery-1.7.1.js - 555 line...

parseJSON: function( data ) {
    if ( typeof data !== "string" || !data ) {
        return null;
    }

    // Make sure leading/trailing whitespace is removed (IE can't handle it)
    data = jQuery.trim( data );

    // Attempt to parse using the native JSON parser first
    if ( window.JSON && window.JSON.parse ) {
        return window.JSON.parse( data );
    }

    // Make sure the incoming data is actual JSON
    // Logic borrowed from http://json.org/json2.js
    if ( rvalidchars.test( data.replace( rvalidescape, "@" )
        .replace( rvalidtokens, "]" )
        .replace( rvalidbraces, "")) ) {

        return ( new Function( "return " + data ) )();

    }
    jQuery.error( "Invalid JSON: " + data );
}





rvalidchars = /^[\],:{}\s]*$/,

rvalidescape = /\\(?:["\\\/bfnrt]|u[0-9a-fA-F]{4})/g,

rvalidtokens = /"[^"\\\n\r]*"|true|false|null|-?\d+(?:\.\d*)?(?:[eE][+\-]?\d+)?/g,

rvalidbraces = /(?:^|:|,)(?:\s*\[)+/g,

Nice. Good argument to use jQuery. – OneWorld Jul 30 '12 at 16:34 — OneWorld, Jul 30 '12 at 16:34
More like an argument to look inside jQuery =) – Olga Mar 22 '13 at 09:42 — Olga, Mar 22 '13 at 09:42

score 13 · Answer 3 · answered Aug 05 '11 at 14:35

The advantage of using json2.js is that it will only install a parser if the browser does not already have one. You can maintain compatibility with older browsers, but use the native JSON parser (which is more secure and faster) if it is available.

Browsers with Native JSON:

IE8+
Firefox 3.1+
Safari 4.0.3+
Opera 10.5+

G.

score 10 · Answer 4 · edited May 23 '17 at 11:55

10

[extending musicfreak comment]

If you are using jQuery, use parseJSON

var obj = jQuery.parseJSON(data)

Internally it checks if browser supports .JSON.parse, and (if available) calls native window.JSON.parse.

If not, does parse itself.

edited May 23 '17 at 11:55

Community

1
1

answered Oct 20 '11 at 23:23

Michael Freidgeim

26,542
16
152
170

score 9 · Answer 5 · answered Nov 18 '13 at 07:53

9

For the benefit of anyone who runs into this thread - for an up-to-date, definitive list of browsers that support the JSON object look here.. A brief generic answer - pretty much all browsers that really matter in the year 2013+.

answered Nov 18 '13 at 07:53

DroidOS

8,530
16
99
171

Browser-native JSON support (window.JSON)

5 Answers5

Linked

Related