jimmywarting
commented
2 years ago Yes, i did mean File System Access.
Browser also sometimes asks for a place to save files. it's pretty much a browser settings weather or not you want to allow auto download. So it's mostly up to each and everyone, and not something you have control over.
there is an alternative option when using the File System Access api to ask for permission to write to a folder if you need to save multiple files. but that ask for more annoying prompts...
I initially thought File System Access was really cool and hoped that Safari and FF would also jump on the train. but they are only going to focus on a browser sandboxed api. So now it's devided up in
- "whatwg/fs" - which only focus on the file api and is mostly just for browsers
- "file-system-access" - which is only for access outside of the browser
file-system-access is also heavily restricted and must follow the annoying "safe browsing" and only allow for atomic writes and not "write in place" so if you wish to append data to a file then if first have to copy that file to a temporary location, modify it, and then replace the old file. which is very costly... doe "whatwg/fs" don't have this issue, it supports non atomic writes (aka write in place)
ivanjx
You have added string
"(legacy-ish)"and note that there is this new native way to save files.Do you mean File System Access API?
Well... it does not allow to save files automatically, without showing the "Save as" dialogue (file picker). For me, only this issue makes this API ~a garbage~ mostly useless as an API for file saving.
I think, auto downloading (saving files without "save as" modal, that can be turns off in the browser settings) is the core thing for a dowloading API, but File System Access API does not support it. So, I would not say, that it's a real alternative.
Or maybe I missed something?