Add $.support for native JSON

[FarSeeing]

Following ​http://dev.jquery.com/ticket/4429:

Would be nice to add a property in $.support to indicate that browser has a native JSON support:

jQuery.support = {

...,

json: typeof JSON === "object"

}

[umbrae]

Patch attached. That rhymes a bit.

[dmethvin]

What's the appropriate name for this property? json? nativeJSON?

If/when this is added, update $.parseJSON to use it.

// Try to use the native JSON parser first
return window.JSON && window.JSON.parse ?

becomes

// Try to use the native JSON parser first
return jQuery.support.nativeJSON ?

[snover]

I can’t help but feel like this will just bloat the code for no reason and would really vote against implementing it. Many of the support tests are fairly complicated and rely on similar markup so it makes sense to run them all at once, but checking for window.JSON is no harder than checking for $.support.json. It’s also shorter.

[john]

Yeah, I agree that's it's quite simple, although we are doing that particular feature test every time parseJSON is called (window.JSON && window.JSON.parse). We could easily offload that to jQuery.support.

[john]

Let's look at this for 1.7.

[john]

Nominating ticket for 1.7 discussion.

[rwaldron]

+0,

[jaubourg]

-1, I really don't see what would be gained from this.

[ajpiano]

-1, This is like putting the treasure map inside of the treasure.

[timmywil]

-1, Unless we want to do our own JSON compatibility functions, I don't see the need.

[danheberden]

-1

[paul.irish]

-1, the detect is trivial, jquery wouldnt help developers with this

[dmethvin]

-1, If we don't need it, I wouldn't add it.

[john]

-1, This really isn't needed, at all.

[scottgonzalez]

-1, Sane detection (and proper detection with Mootools' implementation) are trivial

[jzaefferer]

-1, needs usecase

[cowboy]

-1, $.support.JSON vs window.JSON ? I'll take door number 2, thx

[rwaldron]

Closing per 1.7 roadmap meeting resolution