We've been having an issue with two Angular apps each with several requests made using $http. Sometimes when using Google Chrome, a request would never complete - and there would be no call to any of the promise methods. This never occurred with Firefox or Safari.
After a bit of debugging I figured out that the underlying XmlHttpRequest.onload event was occasionally not being triggered which meant Angular never completed the request. I reported this as a Chrome bug which has since been confirmed: https://code.google.com/p/chromium/issues/detail?id=458970 Our workaround has been to revert to Angular 1.2.x which uses XmlHttpRequest.onreadystatechange rather than XmlHttpRequest.onload. So far the only people who seem to have experience this problem are me and a colleague who are both on developing-world internet... so I have a completely unsubstantiated theory that this problem is more likely to manifest on slow internet connections. Just a heads up in case anyone else runs into this -Rowan -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
