Post by Alex » Mon Nov 26, 2018 4:14 pm
Hello,
Sorry for the delay. We'll try to fix this soon.
However, this is not us doing this, it's due to the change in Chrome browser.
Details:
1. We intercept a download. But we do not cancel it in Chrome immediately, because we're waiting for the response from FDM (download was cancelled or not), so we can cancel it when we need to or allow it to proceed if it was declined in FDM.
2. This worked fine until Chrome changed things. Now, it establishes some timer (around 10 seconds) for any download and waits. If download was not explicitly cancelled, it's allowed to continue by Chrome itself. Thus, we're still waiting for FDM to respond while Chrome resumed the download already.
3. So, we need some algorithm, which will allow us to make a graceful decision to cancel/resume Chrome download during this 10 seconds in all the cases.
We'll think about it. Any suggestions from our users on how it's better to "fix" this are welcome.
Hello,
Sorry for the delay. We'll try to fix this soon.
However, this is not us doing this, it's due to the change in Chrome browser.
Details:
1. We intercept a download. But we do not cancel it in Chrome immediately, because we're waiting for the response from FDM (download was cancelled or not), so we can cancel it when we need to or allow it to proceed if it was declined in FDM.
2. This worked fine until Chrome changed things. Now, it establishes some timer (around 10 seconds) for any download and waits. If download was not explicitly cancelled, it's allowed to continue by Chrome itself. Thus, we're still waiting for FDM to respond while Chrome resumed the download already.
3. So, we need some algorithm, which will allow us to make a graceful decision to cancel/resume Chrome download during this 10 seconds in all the cases.
We'll think about it. Any suggestions from our users on how it's better to "fix" this are welcome.