[Bug] "Allow browser to if canceled" is broken. 275k1h

[anagrammar]

Start a . The fallback to allow the browser to take over seems to be on an arbitrary 10 second timer now. You don't need to click cancel or anything, just wait 10 seconds and FDM throws it back to the browser.

Demo:
https://www.youtube.com/watch?v=4_qsXT7u-6c

[Usher]

Could you follow the reporting rules and provide needed software versions and other details, please?

[anagrammar]

My bad. Chromium 66.0.3359.181 - Win 8.1 - 3.9.7 1638

[Usher]

FDM 3.x stays unchanged for a long time, so there must be something changed in your browser - directly or in installed browser extensions. You haven't reported the way of FDM integration with Chromium - there may be something changed there. You can also test earlier Chromium versions or another Blink-based browsers (Chrome, Opera, Vivaldi…).

[anagrammar]

FDM 3.x stays unchanged for a long time.

I didn't think anything changed with the actual software.

You haven't reported the way of FDM integration with Chromium - there may be something changed there

I'm using the extension you provide. It was just updated the other day, which was when I first noticed this bug.

...there must be something changed in your browser - directly or in installed browser extensions.

Only thing that changed is your integration extension. Here's a demo in Google Chrome, with no extensions enabled except FDM integration:

https://youtu.be/33qaGfiZtFI

Click , wait 10 seconds, FDM throws it back to the browser without any action.

The only real custom setting I use in FDM is to ignore files under 3MB, if that matters:

[johnlgalt]

What is your operating system?

[anagrammar]

What is your operating system?

viewtopic.php?f=1&t=17836#p45837

[johnlgalt]

Yeah, sorry, my browser was having an issue showing me the beginning of the thread, and I missed it last time around.

[spidey]

I have the same issue - except that i noticed it few days ago BEFORE i updated FDM. So i updated FDM thinking it might be 'need to update' reason, but No.. still same issue. So might be a Chrome updated something and created a bug .. //
- -and it doesn't matter if i tick or untick the "Allow browser to .." it still pops up


i am PC / Win 7 PRO / Chrome 66.0.3359.181 (Official Build) (64-bit)
with latest version of FDM / extension etc 5.1.37.7258 (48533e2)

[pete]

Same issue for me. I believe it happened after Chrome updated several months back, and updating Chrome and FDM doesn't fix the issue. Emailed almost 3 months ago, no reply. Please fix this.

[Clive Sorensson]

The issue has been reported, it must be on the list for fixing still.

[pete]

The issue has been reported, it must be on the list for fixing still.

2 months later, can we get started on that list and fix these annoying bugs?

[pete]

And also, I just did a 100% fresh install of Chrome, only ed the FDM extension (no other extensions installed), and this issue still happens, so it's something with your software that isn't meshing with Chrome.

[Usher]

2 months later you still should follow the reporting rules and provide your software versions. Things change, so this request remains valid for ever.

[Alex]

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 . But we do not cancel it in Chrome immediately, because we're waiting for the response from FDM ( 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 and waits. If 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 already.
3. So, we need some algorithm, which will allow us to make a graceful decision to cancel/resume Chrome during this 10 seconds in all the cases.
We'll think about it. Any suggestions from our s on how it's better to "fix" this are welcome.