-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
[feat] FileSystemAccessAPI #13576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just so everyone who stumbles upon this is on the same page, what's shown in those tables here https://developer.mozilla.org/en-US/docs/Web/API/File_System_API#browser_compatibility is outside our control so this would also come down to mostly js-based polyfills, so basically an alternative api design to tauri-plugin-fs. While i keep this open, don't expect the team to work on this, nor to see an officially hosted solution any time soon if at all. |
Apologies I opened this in err, the APIs seem to work without polyfill only in an https environment I haven't tested them all, will update this ticket with my findings |
Actually with safari you can polyfill with https://googlechromelabs.github.io/browser-fs-access/demo/ and it works |
Uh oh!
There was an error while loading. Please reload this page.
Describe the problem
Would love some support for FileSystemAccessAPI, I managed to ponyfill for browser apps of Tauri withboth https://github.com/jimmywarting/native-file-system-adapter/ and browser-fs-access
https://developer.mozilla.org/en-US/docs/Web/API/File_System_API
FileSystemAccess is only available under an https url scheme, but is working with Tauri
Describe the solution you'd like
to be able to have universal fileediting with native app and browser app
Alternatives considered
https://github.com/jimmywarting/native-file-system-adapter/ and browser-fs-access
Additional context
No response
The text was updated successfully, but these errors were encountered: