- From: Sebastian Kippe <notifications@github.com>
- Date: Tue, 27 Feb 2018 08:26:09 +0000 (UTC)
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 27 February 2018 08:26:42 UTC
> If I'm not mistaken, the FileSystem API was only providing sandboxed storage (i.e., although it presents a file-like view, it only presented the web app with a virtual file system, not allowing the app to mount a real directory from the host system Yes, but that actually covers a lot of use cases, like for example @AshleyScirra's and ours. > and thus was isomorphic to LocalStorage or some other API for persistent isolated storage of large amounts of data). There are some important differences between that API and e.g. localStorage/IndexedDB. For example it is not possible to get a filesystem URI for stored objects with the latter, meaning you cannot e.g. play audio or video directly from those. > Either way, this is out of scope for this particular manifest issue, which is about file associations. True. Just wanted to register interest as well. :) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/626#issuecomment-368784685
Received on Tuesday, 27 February 2018 08:26:42 UTC