Reputation: 2405

First Fetch API call cancelled by the second in IE11

I have a ReactJS application that works as expected in Chrome, but fails in IE-11.

The problem is this - we have two drop down lists which are populated from rest services when the page is first loaded. The application is running under SSL. When the page is loaded through IE-11, I get an IE-11 bug issue where the first request call gets cancelled out by the second-the bug is described here:

https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/1282036/

So, I am just asking the community whether there is a work around for IE-11 or is there away to implement my code sequentially where if the first is complete the second is called:

export let getMainData = (dtType, url)=> {
    return dispatch=>{
           dispatch(sendGet(dtType));
           const action = (async(url) => {
                  const response = await fetch(url);
                     let data = await response.json();
                        dispatch(receiveGet(dtType,data));
         });
       action(url);
     };
};

The code above is common code and is used by others in the React App. So what I am thinking if there is away to have a level of abstraction where the two drop down lists can call sequentially and then call the above underneath, perhaps?

Upvotes: 19

Answers (5)

OutstandingBill

Reputation: 2862

Unrelated to ReactJS, but I hope useful to others who land here as I did.

I found the Github fetch polyfill and TaylorHakes' Promise polyfill nice and easy to get started with in the context of my ASP.NET MVC web application. Both were recommended by https://ourcodeworld.com

Upvotes: 3

c-chavez

Reputation: 7496

As pointed out, fetch is not supported by IE11, I also had this problem in my React app. You can, alternatively, use Axios.

If you are migrating (or can migrate), check My answer to this post

Basically, check this code:

Fetch JSON post request

let url = 'https://someurl.com';
let options = {
            method: 'POST',
            mode: 'cors',
            headers: {
                'Accept': 'application/json',
                'Content-Type': 'application/json;charset=UTF-8'
            },
            body: JSON.stringify({
                property_one: value_one,
                property_two: value_two
            })
        };
let response = await fetch(url, options);
let responseOK = response && response.ok;
if (responseOK) {
    let data = await response.json();
    // do something with data
}

Axios JSON post request

let url = 'https://someurl.com';
let options = {
            method: 'POST',
            url: url,
            headers: {
                'Accept': 'application/json',
                'Content-Type': 'application/json;charset=UTF-8'
            },
            data: {
                property_one: value_one,
                property_two: value_two
            }
        };
let response = await axios(options);
let responseOK = response && response.status === 200 && response.statusText === 'OK';
if (responseOK) {
    let data = await response.data;
    // do something with data
}

I always have main request function that the app uses, so it doesn't matter if you use fetch or axios. For example in 'your-common.js':

async function request(url, method, objectData){
    // use axios or fetch or isomorphic-fetch
}

So if your complete app is using your request function, you simply change the library in that function and no harm is done as long as you return the same object or value. You can also wrap the fetch (or axios or whatever http library you use) in a try/catch block to handle promises if using async/await.

Upvotes: 7