Did Chome Change JSON Response Handling?
Is anyone aware of recent changes to Chrome around JSON response handling?
I had written my own JS function to parse JSON. Essentially, it was just a try/catch block with the catch block doing decent error handling since "JSON.parse" fatally fails. I suddenly started getting errors from the catch and in investigating I found that my JSON parse function is no longer needed because the JSON is coming in already parsed into an object. This strikes me as odd and if I haven't changed the back-end API I can only assume something in the middle has changed (the middle being jQuery (bleh!) and Chrome).
As a said note, this forced me to finally look at my app in Firefox and I got some different JS errors, which is "awesome".
Yeah I agree with @kioleanu. If I had to guess it sounds like somewhere in your API you may have been returning a string response in your body but changed it to just send back the JSON object instead. Worth checking out your recent changes to that route or whatever if you're using version control.
Really really unlikely that either Chrome or jQuery changed something. jQuery can parse JSON automatically so you most probably did some changes without realizing. Just check the ajax code between commits and see what you changed