You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Yes it's actually the right behavior. On the web, there is no wide adopted way to open a file saver dialog on every browser. We can only save a file in the download folder.
But the behavior of FileKit is improvable. The best IMO is to be able to open a file saver dialog on platforms that support this feature (everything except web targets) to select the file name and location but without saving anything. It will return a PlatformFile. On PlatformFile, it will exist a new method saveBytes that actually saves bytes to that file and will be accessible from web targets.
So probably in the future, I'll remove the bytes parameter from rememberFileSaverLauncher method and rememberFileSaverLauncher will be only accessible on everything except web targets.
If I use rememberFileSaverLauncher in Desktop compose, it will pop up a dialog allowing me to pick the directory and file name to save to.
In the browser version, it just saves straight to the downloads folder.
I'm not sure if this is platform specific behaviour (if so no problem) or a bug.
The text was updated successfully, but these errors were encountered: