-
Notifications
You must be signed in to change notification settings - Fork 118
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
When will this be available on mobile? #35
Comments
Worked fine for me on Brave, with AndroidOS, in legacy mode. What happened when you tried to use it? |
In legacy mode you can't save over a file you are using. I am not
interested in legacy mode, I want the new api to work on mobile
…On Thu, 15 Apr 2021, 01:05 Anonymous, ***@***.***> wrote:
Worked fine for me on Brave, with AndroidOS, in legacy mode. What happened
when you tried to use it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRRWVMI4VMJ77G4ZTM4EDDTIYUTHANCNFSM426KEAFQ>
.
|
Ah, you're referring to the inability to overwrite existing files. It would be nice to have the new API on mobile, but it's still experimental, I presume that the Chromium developers would put in significantly more effort into making it available on mobile if it is standardized. |
For me the only reason to want to use the new file system api is overcoming that inability. It kind of cripples the UX for progressive web apps on mobile |
You mean the inability of selecting the file name or path when you save a text, don't you? |
The chrome version running on android doesn't support this.
Is there an eta on when it will be or at least note this in the readme.
The current presentation suggest that it falls on legacy mode due to browser version, but that is not true. The same version on desktop supports the new file api.
Chrome on android simply does not allow this at all. When will we get the simple ability to overwrite a file we saved in a pwa?
The text was updated successfully, but these errors were encountered: