*In Chrome.
replyThat file editor seems to work in Firefox. I just tested the save/open functionality.
replyIt's not using the File System Access API, on Firefox it uses <input type="file"> for file-picking, and the save just downloads it. It's not synchronizing anything with your filesystem.
replyDo you know the reason for that? The File System API does seem to be well supported on Firefox: https://developer.mozilla.org/en-US/docs/Web/API/File_System...
replyFirefox unfortunately does not support the File System Access API. You can try by calling the most fundamental function, the one that asks the user to select a file:
reply window.showOpenFilePicker()
This is my main gripe with Firefox. They force their users to either store everything in the cloud or go through the arcane "download" workflow where you have to manually save files.
Iirc the File System Access API should always originate File objects from an input picker so that the user selects the file to be opened and not give more access to apps than users allows?
replyI see. Thanks for enlightening me.
replyIt just downloaded the file on my firefox.
reply*In browsers that have implemented it
replyMy dream is that you could write to Google Drive or iCloud Drive transparently too if the browser allows you to
replyThis is possible with RxDB, you can sync from browser to google drive or ms onedrive
replyI believe you are able to connect to a Google Drive account with a purely client side site via google oauth and then using the Google Drive rest api. There was an article in particular that I liked that walked through it. Let me see if I can find it
replyYes but Google OAuth is a nightmare if you want to "publish" your client so that anyone can use it. If only you use it, you can add yourself as a test user. Just know your access token expires super fast and you will have to frequently re-auth. Its crazy annoying.
replyEven better how about a fully functional VSCode:
https://vscode.dev
replyThe File System Access API makes it possible.