GitHub PushEvent at 2014-03-18 15:20:47
Repository: angular.js
Actor: caitp
Payload: {"shas":[["c869679cee46ddf24cb84f9a5d62858cd66bb2c4","6cc55b7964de8f315966d47f1481d4d6daf08a28@gmail.com","fix($httpBackend): don't error when JSONP callback called with no parameter\n\nThis change brings Angular's JSONP behaviour closer in line with jQuery's. It will no longer treat\na callback called with no data as an error, and will no longer support IE8 via the onreadystatechanged\nevent.\n\nBREAKING CHANGE:\n\nPreviously, the JSONP backend code would support IE8 by relying on the readystatechanged events. This\nis no longer the case, as these events do not provide adequate useful information for deeming whether\nor not a response is an error.\n\nPreviously, a JSONP response which did not pass data into the callback would be given a status of -2,\nand treated as an error. Now, this situation will instead be given a status of 200, despite the lack\nof data. This is useful for interaction with certain APIs.\n\nPreviously, the onload and onerror callbacks were added to the JSONP script tag. These have been\nreplaced with jQuery events, in order to gain access to the event object. This means that it is now\ndifficult to test if the callbacks are registered or not. This is possible with jQuery, using the\n$.data(\"events\") method, however it is currently impossible with jqLite. This is not expected to\nbreak applications.\n\nCloses #4987","Caitlin Potter",true]],"size":1,"ref":"refs/heads/issue-4987","head":"c869679cee46ddf24cb84f9a5d62858cd66bb2c4"}