Child Item

Set the timeout to close the chooser after few seconds of selecting the files or

Once user choose the files and click the submit button in web application dropbox chooser I'm downloading the files in my backend by calling ajax function in success option of the chooser, if the file is too large then the chooser stays open for few minutes (even after user selects and submit the files) untill the whole video gets downloaded in backend, is there any option to close the popup of chooser after few seconds, so that download continue in the background and user will not be confused that why the webpage is stuck.

Find more posts tagged with

Developers

Comments

Здравко

@Ashrafali wrote:
..., if the file is too large then the chooser stays open ...

Hi @Ashrafali,

Do you perform file operations in chooser's callback or let it return before (or immediately after) start processing? 🧐 Take in mind that chooser will stay blocked as much as you block it's execution within the callback. 😉 Make your processing little more asynchronous.

Hope this gives direction.

Ashrafali

Thankyou, I got it but is there any option to close it? or hide it? If there is no options then I have different approach for that but just wants to know if there is any option to close or hide.

Greg-DB

@Ashrafali No, there isn't an option to close or hide it explicitly. It will automatically close. As Здравко said, it sounds like the issue here is that you're blocking the callback. You should move your operations out of the callback as they said, so that it will automatically close quickly.

Здравко

@Ashrafali, I'm wrong in my previous post. Seems 'success' callback is called asynchronously. That's why it can't stop/delay chooser disappearance.

To be honest I can't reproduce your issue. 🤔 Can you share some code sniped representing it?

Greg-DB

For reference, I can reproduce this, but only in some browsers (e.g., Chrome but not Firefox), so there seems to be some browser-specific implementation details that affect this.

In any case, it still sounds like the right solution here is to move the long work out of the callback.

Здравко

@Greg-DB wrote:
...
In any case, it still sounds like the right solution here is to move the long work out of the callback.

Yes, one simple "fix" (might not be the best in all cases) can be replace function declaration like:

success: function(files) {

to something like:

success: async function(files) {

And yes, on Firefox it works with and without 'async'. I hope it will work on Chrome too (haven't tested it yet).

Good luck @Ashrafali!