data-* attribute parsing bypasses jQuery.parseJSON (inconsistent with 1.x)

[gibson042]

2.x data-* attribute parsing directly utilizes JSON.parse, in contrast to both 1.x and the rest of the codebase (i.e., ​ajax). We should probably switch back to jQuery.parseJSON, but could alternatively switch ajax to JSON.parse. I prefer the former mostly for 1.x consistency.

[dmethvin]

I agree this should all go through the same path.

[Timmy Willison]

+1 for former

[Rick Waldron]

In jQuery 2.x:

(src/ajax/parseJSON.js)

jQuery.parseJSON = JSON.parse;

(src/data.js)

rbrace.test( data ) ? JSON.parse( data ) :

How does it benefit jQuery to go through an alias to the same function?

[gibson042]

Replying to rwaldron:

How does it benefit jQuery to go through an alias to the same function?

Duckpunching in a spy (which is how I came across the ​1.x/2.x discrepancy) or a behavior tweak (e.g., for jQuery migrate and #13169).

[Rick Waldron]

Replying to gibson042:

Replying to rwaldron:

How does it benefit jQuery to go through an alias to the same function?

Duckpunching in a spy

Seems reasonable enough. +1

[Richard Gibson]

Fix #14459: Use jQuery.parseJSON instead of JSON.parse

Changeset: ced9d155f010bc456745a55a63ca959db9d405d3