Use FileSaver.js on WASM

[dolezvo1]

Use FileSaver.js on WASM to allow for default file names on "recent" versions of all major browsers (see supported browsers). I think it is related to what #128 is asking for.

[PolyMeilex]

Look promising, thanks!

But the UX seems to be broken after this change, the popup no longer serves any purpose as far as I can tell, shouldn't we remove it?

Firefox:

Screencast.From.2025-10-18.17-21-42.mp4

Chrome:

Screencast.From.2025-10-18.17-22-21.mp4

[dolezvo1]

I think it could be removed, but if I understand correctly, FileSaver.js doesn't really support cancellation. I wasn't sure to what extent is cancellation necessary, so I didn't touch the rest of the code.

[PolyMeilex]

It's fine we don't need cancellation, from what I've seen most people were not fans of the popup existence anyway.

[dolezvo1]

Now that I think about it, I think the alternative to removing it could be adding download button that would allow for triggering the download multiple times, similar to how the link worked up until this. I'm not sure what is the situation with WebKit (with downloads not being triggered outside of input handling) at the moment, but presumably better to err on the side of safety.

[PolyMeilex]

Now that I think about it, I think the alternative to removing it could be adding download button that would allow for triggering the download multiple times, similar to how the link worked up until this.

Sure, that's also fine by me. Having a button also makes sure that we will be called from a click-handler, which as you mentioned can sometimes be mandatory.

[dolezvo1]

Awesome, I'll try to do it as soon as possible. Thanks for taking a look!

[dolezvo1]

Could you check if this works?

[PolyMeilex]

Works fine now.

Can you also say which browser it actually fixes?
File names in Firefox 143.0.4 and Chrome 141.0.7390.107 both work fine for me on rfd master.

[dolezvo1]

Oh, I was operating under the assumption that it didn't, but you're right. I think that means the documentation for AsyncFileDialog is wrong, though.