Angular.JS ajax request failing (stuck in pending) in MS Edge only

Fixed Issue #10584561

Details

Author
Ben G.
Created
Jan 19, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 6 people

Sign in to watch or report this issue.

Steps to reproduce

http://www.naidex.co.uk/consumer/exhibitors/ throws an Edge-specific problem, with angular ajax requests not loading the returned data from an api call. Looking at the edge debugger, with no timeout the request just sits in “pending” indefinitely, or if I set a timeout (of eg 20s) then the ajax error handler is called after that time… but weirdly the “received” column in the debugger shows the correct data size of the json I would expect to be returned.

The ajax request (to webapi.bstartup.com/api_exhibitors/3203/ ) returns successfully in all other browsers including IE

A request to the exact same API, using Edge, from www.farmbusinessshow.co.uk/exhibitors/ is also successful.

Finally, if I reduce the size of the json returned to ~ 6Kb, then the issue stops and the request returns as successful. Using Edge, this page http://www.naidex.co.uk/partners/
loads the json successfully about 50% of the time, with the json payload returned from webapi.bstartup.com/api_supporters/3203/ being 7.69Kb

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To from “Brad E.” to “Scott W.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “Fixed”

    • Thank you for filing this bug Ben! This issue has been resolved and the fix will be available in an upcoming Windows Insider build.

    • I am having this issue when one of my iframes are hidden using “display:none” and page crashes. Here is the sample http://acitest.azurewebsites.net/acitest.html

    • @Ali I’ve had a similar problem reported to me with IE11 on Windows 7. JSON is around 116KB and the browser just indefinitely hangs. Seems to work fine on Edge and IE on windows 10, as well as FF and Chrome. Not sure if it is an issue with the degree of nested objects in the JSON or the max length of the response. Reducing the size seems to correct the problem, but that is not a viable solve for me. Can you share details of the underlying issue and should I expect this reported fix to apply to my issue?

    You need to sign in to your Microsoft account to add a comment.

    Sign in