Clicking anchor link to download file causes page load timeout #14857

hiatien19 · 2021-02-02T01:34:12Z

i was update Cypress 6.4.0
but i cannot click button download

file source:

jennifer-shehane · 2021-02-03T08:13:49Z

I can recreate this error with the test code below:

it('download file', ({ pageLoadTimeout: 5000 }), () => {
  cy.visit('https://people.sc.fsu.edu/~jburkardt/data/csv/csv.html')
  cy.get('a[href="addresses.csv"]').click()
})

sarja510 · 2021-02-18T12:32:56Z

I am facing the same problem. Clicking on the Download button change window.location.href to download the file, also triggers the beforeunload event. We are downloading the file only, not redirecting towards a page actually, but for the redirection, cypress wait for a load event to be triggered by the application but as no redirection actually is happening it gets page load timeout error. I tried stopPropagation on "window:before:unload" event but didn't work. If we can invoke the load event during the wait or can execute the stopPropagation on the correct state it can be resolved I guess.

Cypress version: 6.5.0
OS : Windows 10

kiransurakanti · 2021-02-22T06:57:18Z

Hi, @jennifer-shehane I'm also facing the same issue even after updating Cypress 6.5.0. Clicking on a button downloads the file, but after downloading the file, the cypress waiting for page load which is not the expected behavior. please suggest a workaround for this problem.

sarja510 · 2021-02-25T08:32:26Z

I got a workaround with the following issue,

What actually was happening in my case is that after clicking the download button a redirection was happening to download the file. From the application code: window.location.href was changing to download the file on click event. When cypress gets the redirection it waits for a page load event to get fired from AUT for continuing further. As no actual page redirection was happening so it got stuck and got page load timeout. So I tried the following workaround and it is working fine for my case:

Solution/Workaround:

All I needed was to fire a page load event to execute other cypress commands after clicking the download button rather than getting page load timeout. So before clicking the Download button or targeted file I added an event listener ‘click’ to listen out for the event and did something to trigger the page load event. Here is a tricky part, on event handling I triggered window.location.reload. But if I instantly trigger that on click event it will work but the file will not get downloaded. So I set a timeout of 5 sec, it may vary as per our requirement to download the file, after that, I am triggering window.document.location.reload(). This reloads the page and triggers a page load event. As soon as cypress get the page load event it continues executing further commands

the following solution worked for me fine:

cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  cy.get('[ng-click="vm.export()"]').click()
})

I hope cypress will give a proper solution for this case, till then anyone can use this workaround. @jennifer-shehane @hiatien19 @kiransurakanti

AdrianHL · 2021-03-02T14:39:59Z

I'm experiencing the same issue here. The solution proposed by @sarja510 works until a new version fix it.

mklepaczewski · 2021-03-04T16:56:23Z

the following solution worked for me fine:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  cy.get('[ng-click="vm.export()"]').click()
})
I hope cypress will give a proper solution for this case, till then anyone can use this workaround. @jennifer-shehane @hiatien19 @kiransurakanti

Unfortunately, this doesn't seem to be enough. The test seems to succeed even if the file to be downloaded doesn't exist (404s etc.). You can confirm it by changing URL of the file to be downloaded:

cy.intercept('/', (req) => {
    req.url += '-this-url-doesnt-exist';
});

I fixed it by intercepting the request and checking the status code of the response:

cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  
  /* Make sure the file exists */
  cy.intercept('/', (req) => {
    req.reply((res) => {
      expect(res.statusCode).to.equal(200);
    });
  });

  cy.get('[ng-click="vm.export()"]').click()
})

JoeKellyFR · 2021-03-15T18:52:25Z

@mklepaczewski This solution worked for me, thanks, and also to @sarja510 for the original approach. huge relief to be unblocked!

swatiamberkar · 2021-03-18T07:26:28Z

@jennifer-shehane

I got a workaround with the following issue,

What actually was happening in my case is that after clicking the download button a redirection was happening to download the file. From the application code: window.location.href was changing to download the file on click event. When cypress gets the redirection it waits for a page load event to get fired from AUT for continuing further. As no actual page redirection was happening so it got stuck and got page load timeout. So I tried the following workaround and it is working fine for my case:

Solution/Workaround:

All I needed was to fire a page load event to execute other cypress commands after clicking the download button rather than getting page load timeout. So before clicking the Download button or targeted file I added an event listener ‘click’ to listen out for the event and did something to trigger the page load event. Here is a tricky part, on event handling I triggered window.location.reload. But if I instantly trigger that on click event it will work but the file will not get downloaded. So I set a timeout of 5 sec, it may vary as per our requirement to download the file, after that, I am triggering window.document.location.reload(). This reloads the page and triggers a page load event. As soon as cypress get the page load event it continues executing further commands

the following solution worked for me fine:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  cy.get('[ng-click="vm.export()"]').click()
})
I hope cypress will give a proper solution for this case, till then anyone can use this workaround. @jennifer-shehane @hiatien19 @kiransurakanti

@sarja510 This solution is worked for me.Thank You.

shilpajain09 · 2021-03-31T20:27:18Z

This might be a very stupid question, but can you please let me know what is this doing

cy.get('[ng-click="vm.export()"]').click()

@mklepaczewski

mklepaczewski · 2021-03-31T20:34:13Z

This might be a very stupid question, but can you please let me know what is this doing

cy.get('[ng-click="vm.export()"]').click()

@mklepaczewski

ng-click="vm.export()" is just a selector. It clicks the first(?) element with attribute ng-click="vm.export()". So, for example if I had this in HTML:

<a href="https://example.com/" ng-click="vm.export()">Click here</a>

then the mentioned line would find this element and click it. If your link/button has id my-button then you would replace it with something like cy.get('#my-button').click()

shilpajain09 · 2021-03-31T20:42:56Z

@mklepaczewski thanks a lot for your prompt response.

Are we verifying somewhere that the file is downloaded successfully?

noothaithinh · 2021-04-08T10:39:34Z

@mklepaczewski thanks a lot for your prompt response.

Are we verifying somewhere that the file is downloaded successfully?

You can find it in Cypress.config('downloadsFolder');

MCFreddie777 · 2021-05-20T12:21:58Z

Any updates on this? Will it be released soon?

yasinitskyi · 2021-06-24T12:26:24Z

@jennifer-shehane when are you going to release patch for this issue, it is huge bug, it is 7.5.0 already and no cure of this

samanthakirby · 2021-07-21T23:07:47Z

Hitting this all over the place as well. I'm glad it's not just me struggling with it. Added a watch to this. Hopefully it gets sorted soon :)

Jacek-fstack · 2021-08-02T12:07:22Z

Any chance for a fix for this? 8.1 and bug still is standing strong

mac503 · 2021-08-11T16:51:51Z

We are also struggling with this. A fix would be really great! Thanks

bahmutov · 2021-09-16T21:38:01Z

@sarja510 pretty slick, love it, and it is working for me :)

devsrihari4 · 2021-09-27T16:02:19Z

Facing the same issue. Any solution?

faith-berroya · 2022-07-11T03:40:24Z

Hello, I'm still encountering this issue using 9.6.0. :/ The workaround is working perfectly in Chrome but in Firefox it's not allowing it to reload. Hmmm.

imadx · 2022-07-21T06:14:19Z

For anyone who cannot afford page reloads in the middle of a test, I used the following to catch the error and continue.

Cypress.on("uncaught:exception", (error) => {
  if (
    error.message.includes(
      "Timed out after waiting `5000ms` for your remote page to load",
    )
  ) {
    return false;
  }
});

Cypress.on("fail", (error) => {
  if (
    error.message.includes(
      "Timed out after waiting `5000ms` for your remote page to load",
    )
  ) {
    return false;
  }

  throw error;
});

The timeout 5000ms which is different from the default timeout was set within the test with the following and is being reset later down the test.

Cypress.config("pageLoadTimeout", 5000);

Hacky... but worked for me

MateuszKobiera · 2022-10-17T11:54:46Z

This bug is super annoying and sometimes does happen and sometimes does not on run in a pipeline. Workaround is great for openMode but does not work if bug suddenly does not occur in runMode in pipeline. @jennifer-shehane do you have maybe any update on this ticket?

Raphhinha · 2022-10-24T19:23:40Z

For anyone who cannot afford page reloads in the middle of a test, I used the following to catch the error and continue.
Cypress.on("uncaught:exception", (error) => {
  if (
    error.message.includes(
      "Timed out after waiting `5000ms` for your remote page to load",
    )
  ) {
    return false;
  }
});

Cypress.on("fail", (error) => {
  if (
    error.message.includes(
      "Timed out after waiting `5000ms` for your remote page to load",
    )
  ) {
    return false;
  }

  throw error;
});
The timeout 5000ms which is different from the default timeout was set within the test with the following and is being reset later down the test.
Cypress.config("pageLoadTimeout", 5000);
Hacky... but worked for me

Where can I include this code?

Sorry I am new to Cypress

gvaatstra · 2022-10-25T07:05:39Z

The solution found here worked for me:
#1551 (comment)

In my case I download a CSV by a form submit. I can intercept the request, validate the response headers, change the response headers and then even validate data on the page as it renders the CSV as text (and obviously no load event issue anymore)
Pro's are that you don't need any dirty timeout and can validate the data. In my opinion the download functionality is browser functionality based on the headers, so by validating the headers, I'm confident that it will download.
Con is that you don't have a file downloaded.

theTestingApproach · 2022-11-17T13:05:42Z

the following solution worked for me fine:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  cy.get('[ng-click="vm.export()"]').click()
})
I hope cypress will give a proper solution for this case, till then anyone can use this workaround. @jennifer-shehane @hiatien19 @kiransurakanti
Unfortunately, this doesn't seem to be enough. The test seems to succeed even if the file to be downloaded doesn't exist (404s etc.). You can confirm it by changing URL of the file to be downloaded:
cy.intercept('/', (req) => {
    req.url += '-this-url-doesnt-exist';
});
I fixed it by intercepting the request and checking the status code of the response:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  
  /* Make sure the file exists */
  cy.intercept('/', (req) => {
    req.reply((res) => {
      expect(res.statusCode).to.equal(200);
    });
  });

  cy.get('[ng-click="vm.export()"]').click()
})

the following solution worked for me fine:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  cy.get('[ng-click="vm.export()"]').click()
})
I hope cypress will give a proper solution for this case, till then anyone can use this workaround. @jennifer-shehane @hiatien19 @kiransurakanti
Unfortunately, this doesn't seem to be enough. The test seems to succeed even if the file to be downloaded doesn't exist (404s etc.). You can confirm it by changing URL of the file to be downloaded:
cy.intercept('/', (req) => {
    req.url += '-this-url-doesnt-exist';
});
I fixed it by intercepting the request and checking the status code of the response:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  
  /* Make sure the file exists */
  cy.intercept('/', (req) => {
    req.reply((res) => {
      expect(res.statusCode).to.equal(200);
    });
  });

  cy.get('[ng-click="vm.export()"]').click()
})
But what @sarja510 says is that this block of code should be placed before clicking the button that triggers download. Your modification sets the interception before the download starts which cause error "No request ever occurred." and it makes sense.

Did I misunderstand your solution?

I got a workaround with the following issue,

What actually was happening in my case is that after clicking the download button a redirection was happening to download the file. From the application code: window.location.href was changing to download the file on click event. When cypress gets the redirection it waits for a page load event to get fired from AUT for continuing further. As no actual page redirection was happening so it got stuck and got page load timeout. So I tried the following workaround and it is working fine for my case:

Solution/Workaround:

All I needed was to fire a page load event to execute other cypress commands after clicking the download button rather than getting page load timeout. So before clicking the Download button or targeted file I added an event listener ‘click’ to listen out for the event and did something to trigger the page load event. Here is a tricky part, on event handling I triggered window.location.reload. But if I instantly trigger that on click event it will work but the file will not get downloaded. So I set a timeout of 5 sec, it may vary as per our requirement to download the file, after that, I am triggering window.document.location.reload(). This reloads the page and triggers a page load event. As soon as cypress get the page load event it continues executing further commands

the following solution worked for me fine:
cy.window().document().then(function (doc) {
  doc.addEventListener('click', () => {
    setTimeout(function () { doc.location.reload() }, 5000)
  })
  cy.get('[ng-click="vm.export()"]').click()
})
I hope cypress will give a proper solution for this case, till then anyone can use this workaround. @jennifer-shehane @hiatien19 @kiransurakanti

From here how do you check if the file has actually been downloaded..Anything done after this step is causing page load issue

ghost · 2022-11-28T11:50:57Z

hi all, we've been struggling with this issue and seems like we finally found a working solution that doesn't include arbitrary timeouts and works consistently. There're alternative ways to do this involving using cy.state but we decided to avoid using that non-documented method as it might be removed/changed in the future. This piece of code should be inserted before the action triggering your download:

  cy.window().then(win => {
    const triggerAutIframeLoad = () => {
      const AUT_IFRAME_SELECTOR = '.aut-iframe';

      // get the application iframe
      const autIframe = win.parent.document.querySelector(AUT_IFRAME_SELECTOR);

      if (!autIframe) {
        throw new ReferenceError(`Failed to get the application frame using the selector '${AUT_IFRAME_SELECTOR}'`);
      }

      autIframe.dispatchEvent(new Event('load'));
      // remove the event listener to prevent it from firing the load event before each next unload (basically before each successive test)
      win.removeEventListener('beforeunload', triggerAutIframeLoad);
    };

    win.addEventListener('beforeunload', triggerAutIframeLoad);
  });

tina-zeng · 2022-12-06T08:59:09Z

hi all, we've been struggling with this issue and seems like we finally found a working solution that doesn't include arbitrary timeouts and works consistently. There're alternative ways to do this involving using cy.state but we decided to avoid using that non-documented method as it might be removed/changed in the future. This piece of code should be inserted before the action triggering your download:
  cy.window().then(win => {
    const triggerAutIframeLoad = () => {
      const AUT_IFRAME_SELECTOR = '.aut-iframe';

      // get the application iframe
      const autIframe = win.parent.document.querySelector(AUT_IFRAME_SELECTOR);

      if (!autIframe) {
        throw new ReferenceError(`Failed to get the application frame using the selector '${AUT_IFRAME_SELECTOR}'`);
      }

      autIframe.dispatchEvent(new Event('load'));
      // remove the event listener to prevent it from firing the load event before each next unload (basically before each successive test)
      win.removeEventListener('beforeunload', triggerAutIframeLoad);
    };

    win.addEventListener('beforeunload', triggerAutIframeLoad);
  });

This code helps me find the root cause of my page load time-out issue! Thanks! I've commented here

irensoltan · 2023-01-12T19:57:58Z

@jennifer-shehane @brian-mann - are there any updates on this? We would expect Cy to gracefully handle this kind of problem. Instead, the issue is lingering around for years and we users are forced into using hacky work arounds. Can we have an update on when this will be solved?

sanghamitrabytepitch · 2023-02-19T12:33:06Z

I have a similar situation where i tried downloading a file. However, my download option is available inside a modal pop-up. Hence, the above workarounds doesn't seem to quite work for me. Any resolution/input on the same could really help!!

luciarodriguez · 2023-03-08T23:37:00Z

Same issue happening for me with Cypress 12.6.0 in Chrome 110. Is there no patch yet?
The code mentioned above with the timeouts does not work for me. Still getting the load error

gvaatstra · 2023-03-09T07:51:24Z

I do understand it's a problem, but for the people asking for a fix or a patch, I'd like to hear how you would see this working. Cypress simply relies on a load event that never comes in this case and if it wouldn't do that, it would impact the 99,9% of the cases where they use it for stability.

They have the downloadfile method you can use.
Really consider what you're actually testing and what you expect

If you know the path to the file, it's simple. Use the downloadfile method, because elseway you're simply testing browser functionality.
If you don't know the path to the file, you can use multiple workarounds. For example, I change the headers to show content on the screen (and therefore have no issue with the load event). That works well for content that can be shown in the browser (like CSV). I posted that in this issue.
Another way is validating that the content contains something you expect. f.e. that it's a docx. by using a cy.get

    cy.get("#button_download")
      .closest("form")
      .invoke("attr", "action")
      .then((actionLink) => {
        cy.api("GET", actionLink).then((response) => {
          expect(response.body).to.contain("word/document.xml");
        });
      });

I think that is enough to test and I'd be curious what you want to test with Cypress on a downloaded file anyway.

ntvinhit · 2023-03-22T08:42:47Z

For anyone who cannot afford page reloads in the middle of a test, I used the following to catch the error and continue.
Cypress.on("uncaught:exception", (error) => {
  if (
    error.message.includes(
      "Timed out after waiting `5000ms` for your remote page to load",
    )
  ) {
    return false;
  }
});

Cypress.on("fail", (error) => {
  if (
    error.message.includes(
      "Timed out after waiting `5000ms` for your remote page to load",
    )
  ) {
    return false;
  }

  throw error;
});
The timeout 5000ms which is different from the default timeout was set within the test with the following and is being reset later down the test.
Cypress.config("pageLoadTimeout", 5000);
Hacky... but worked for me

It's not work because it never goes to uncaught:exception and if we return false on fail event, the test will pass.

zbjornson · 2023-04-18T05:42:30Z

I spent a long time investigating this. Cypress sets up listeners for page "stability" in a beforeunload handler. beforeunload fires when a form is submitted, but if the form doesn't result in a page load (e.g. because the response has a Content-Disposition: attachment header), then Cypress hangs.

These are the relevant parts of the HTML spec

form submission
- step 23.4.2 submit the form -> navigate
beginning navigation
- step 16.1 fires beforeunload
7.4.5 populating a session history entry
- Step 10 covers handling of Content-Disposition: attachment responses. Compare to...
- Step 11, which is a normal navigation that loads a document and causes the "load" event to fire (see e.g. this for content-type: text/html). There is no navigation from a download in step 10. This is what Cypress got wrong.

This is the most reliable solution I came up with and the same logic I think Cypress should have in its core:

// in your commands.mjs file
Cypress.Commands.add("suppressWaitForPageLoad", function () {
	cy.intercept("*", req => {
		req.on("before:response", res => {
			const isDownload = res.headers["content-disposition"]?.startsWith("attachment");
			// Need to exclude requests not made by the application, such as
			// background browser requests.
			const origin = cy.getRemoteLocation("origin");
			const isFromAUT = req.headers["referer"]?.startsWith(origin);
			if (isDownload && isFromAUT) {
				Cypress.log({
					name: "suppressWaitForPageLoad",
					message: "Bypassing wait for page load event because response has Content-Disposition: attachment"
				});
				cy.isStable(true, "load");
			}
		});
	});
});

Then use it like:

cy.suppressWaitForPageLoad();
cy.contains("button", "Download").click();

Firing a synthetic "load" event as shown in the post above can cause other issues. A page is only ever supposed to have one "load" event fired.

gvaatstra · 2023-04-18T06:48:17Z

@zbjornson, that seems like very good research and a nice solution! Is the cy.isStable(true, "load") another custom function?
I haven't tested it (and simply wanted to acknowledge the effort you put into the issue), but I can imagine that if people want to use this, it could be beneficial to add a check after the download. For example, that the file is fully downloaded). Also I'd go for adding a parameter for the path specifically (instead of the *) to limit the the risk of side-effects. That also helps in adding a unique alias and if you add an alias, you probably can also wait for the request to finish.

Songyu-Wang · 2023-05-11T18:19:20Z

I do understand it's a problem, but for the people asking for a fix or a patch, I'd like to hear how you would see this working. Cypress simply relies on a load event that never comes in this case and if it wouldn't do that, it would impact the 99,9% of the cases where they use it for stability.

They have the downloadfile method you can use.

Really consider what you're actually testing and what you expect

If you know the path to the file, it's simple. Use the downloadfile method, because elseway you're simply testing browser functionality. If you don't know the path to the file, you can use multiple workarounds. For example, I change the headers to show content on the screen (and therefore have no issue with the load event). That works well for content that can be shown in the browser (like CSV). I posted that in this issue. Another way is validating that the content contains something you expect. f.e. that it's a docx. by using a cy.get
    cy.get("#button_download")
      .closest("form")
      .invoke("attr", "action")
      .then((actionLink) => {
        cy.api("GET", actionLink).then((response) => {
          expect(response.body).to.contain("word/document.xml");
        });
      });
I think that is enough to test and I'd be curious what you want to test with Cypress on a downloaded file anyway.

@gvaatstra
I think you probably would agree all the workarounds mentioned are not prefect.
For example,

If the webpage's state is updated by user actions which are not yet permanently saved. A reload call could destroy all the progress and force the test to redo all the actions before continue the tests
Displaying files instead of downloading can only be applied to limited file types. Also, once displayed, a new tab is created and there is nothing we can do to get back to the old page unless we hack it with chrome-remote-interface
We may also want to E2ely test the file content if they are dramatically generated so checking the url in html is not sufficient
...

I think a good first step is to just add a flag to bypass the "load" check globally and advanced test writers can decide when and how to (dis)able it. We dont need it to be prefect, we just need a way to get stuff done

Brugui7 · 2023-10-31T16:15:32Z

I don't know if this has been said before by someone else but if you're sure that you're clicking on a download link, you can workaround the issue by adding the download attribute to the html element before clicking it:

cy.get(a)
  .then(($a) => {
    $a.attr("download", ""); 
  })
.click();

That way the browser won't trigger the page change event and Cypress won't wait for a loadPage event.

cypress-bot · 2023-11-08T23:28:33Z

Released in 13.5.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.5.0, please open a new issue.

jennifer-shehane added the topic: downloads ⬇️ label Feb 3, 2021

jennifer-shehane added the type: bug label Feb 3, 2021

cypress-bot bot added the stage: ready for work The issue is reproducible and in scope label Feb 3, 2021

jennifer-shehane changed the title ~~Cannot click button download in cypress 6.4.0~~ Clicking anchor link to download file causes page load timeout Feb 3, 2021

This was referenced Feb 5, 2021

Cannot click button download in cypress 6.3.0 #14792

Closed

Don't wait for page load when clicking a download link #8089

Closed

czende mentioned this issue Feb 12, 2021

Parse Error: Header overflow Xvier/cypress-downloadfile#16

Closed

jennifer-shehane mentioned this issue Feb 26, 2021

Clicking on anchor elements expects a page load event #15220

Closed

ngandymov mentioned this issue Mar 16, 2021

Downloading dynamically generated file fails when Cypress does not detect page load #14789

Closed

ajgray2017 mentioned this issue Apr 24, 2021

File download issue, after that page visit times out #15161

Closed

manasaj111 mentioned this issue Jun 10, 2021

Ability to prevent/stop loading 'Page load' #7083

Open

noahgildersleeve mentioned this issue Jun 1, 2022

regression: UI harvester/tests#354

Merged

mschile added the routed-to-e2e label Nov 4, 2022

mdhont mentioned this issue Nov 10, 2022

[bitnami/ejbca] Fix EJBCA Cypress Test bitnami/charts#13465

Closed

nagash77 added the prevent-stale mark an issue so it is ignored by stale[bot] label Apr 3, 2023

nagash77 added E2E Issue related to end-to-end testing Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. and removed routed-to-e2e labels Apr 19, 2023

emilyrohrbough added a commit that referenced this issue Nov 2, 2023

fix: handle page loads when download is triggered #14857

4244eb0

emilyrohrbough mentioned this issue Nov 2, 2023

fix: handle download from element missing download attribute #28222

Merged

3 tasks

emilyrohrbough closed this as completed in #28222 Nov 6, 2023

cypress-bot bot removed the stage: backlog label Nov 8, 2023

cypress-bot bot locked as resolved and limited conversation to collaborators Nov 8, 2023

Clicking anchor link to download file causes page load timeout #14857

Clicking anchor link to download file causes page load timeout #14857

Comments

hiatien19 commented Feb 2, 2021

jennifer-shehane commented Feb 3, 2021 • edited

sarja510 commented Feb 18, 2021

kiransurakanti commented Feb 22, 2021 • edited

sarja510 commented Feb 25, 2021 • edited by jennifer-shehane

AdrianHL commented Mar 2, 2021

mklepaczewski commented Mar 4, 2021 • edited

JoeKellyFR commented Mar 15, 2021

swatiamberkar commented Mar 18, 2021

shilpajain09 commented Mar 31, 2021 • edited

mklepaczewski commented Mar 31, 2021

shilpajain09 commented Mar 31, 2021

noothaithinh commented Apr 8, 2021

MCFreddie777 commented May 20, 2021

yasinitskyi commented Jun 24, 2021

samanthakirby commented Jul 21, 2021

Jacek-fstack commented Aug 2, 2021

mac503 commented Aug 11, 2021

bahmutov commented Sep 16, 2021

devsrihari4 commented Sep 27, 2021

faith-berroya commented Jul 11, 2022

imadx commented Jul 21, 2022

MateuszKobiera commented Oct 17, 2022 • edited

Raphhinha commented Oct 24, 2022

gvaatstra commented Oct 25, 2022

theTestingApproach commented Nov 17, 2022

ghost commented Nov 28, 2022 • edited by ghost

tina-zeng commented Dec 6, 2022 • edited

irensoltan commented Jan 12, 2023

sanghamitrabytepitch commented Feb 19, 2023

luciarodriguez commented Mar 8, 2023 • edited

gvaatstra commented Mar 9, 2023 • edited

ntvinhit commented Mar 22, 2023 • edited

zbjornson commented Apr 18, 2023

This is the most reliable solution I came up with and the same logic I think Cypress should have in its core:

gvaatstra commented Apr 18, 2023

Songyu-Wang commented May 11, 2023 • edited

Brugui7 commented Oct 31, 2023

cypress-bot bot commented Nov 8, 2023

jennifer-shehane commented Feb 3, 2021 •

edited

kiransurakanti commented Feb 22, 2021 •

edited

sarja510 commented Feb 25, 2021 •

edited by jennifer-shehane

mklepaczewski commented Mar 4, 2021 •

edited

shilpajain09 commented Mar 31, 2021 •

edited

MateuszKobiera commented Oct 17, 2022 •

edited

ghost commented Nov 28, 2022 •

edited by ghost

tina-zeng commented Dec 6, 2022 •

edited

luciarodriguez commented Mar 8, 2023 •

edited

gvaatstra commented Mar 9, 2023 •

edited

ntvinhit commented Mar 22, 2023 •

edited

Songyu-Wang commented May 11, 2023 •

edited