Can we remove our silly JSON.stringify polyfill from examples?

[gnarf]

http://caniuse.com/#search=json - support back to IE8

The example in jQuery.extend() has a pretty complex "fake stringify" method and seems overly complex for todays needs.

api.jquery.com/entries/jQuery.extend.xml

Line 59 in 03fcbfb

var printObj = typeof JSON !== "undefined" ? JSON.stringify : function( obj ) {

[arthurvr]

I wouldn't do it in master yet, as people might just copy-paste and be confused because jQuery 1.x is compatible with IE6+. That being said, I think we can just do this in the v3.0.0-docs branch, as there we don't have to support IE8 anyways.

[arthurvr]

I can PR if everybody agrees.

[gnarf]

We could also just use http://api.jquery.com/jQuery.param/ instead? I just
want to simply the example...

On Wed, Feb 18, 2015 at 11:27 AM, Arthur Verschaeve <
notifications@github.com> wrote:

I wouldn't do it in master yet, as people might just copy-paste and be
confused because jQuery 1.x is compatible with IE6+. That being said, I
think we can just do this in the v3.0.0-docs branch, as there we don't
have to support IE8 anyways.

—
Reply to this email directly or view it on GitHub
#658 (comment)
.

[arthurvr]

JSON is a little more readable IMHO, but fine with that as well.

[gnarf]

I Agree that JSON is indeed more readable... I just don't think that JSON
encoder we have in the example is at all readable, and it confuses the
examples quite a bit to try and parse it.

On Wed, Feb 18, 2015 at 11:31 AM, Arthur Verschaeve <
notifications@github.com> wrote:

JSON is a little more readable IMHO, but fine with that as well.

—
Reply to this email directly or view it on GitHub
#658 (comment)
.

[arthurvr]

PR gh-661.