- From: Matt Giuca <notifications@github.com>
- Date: Tue, 27 Feb 2018 07:23:07 +0000 (UTC)
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 27 February 2018 07:23:30 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, and thus was isomorphic to LocalStorage or some other API for persistent isolated storage of large amounts of data). What I think we are talking about here (what [chrome.fileSystem](https://developer.chrome.com/apps/fileSystem) was) is an API to ask the user to nominate (through UI) a folder on their system, and provide persistent access to that non-sandboxed directory. Either way, this is out of scope for this particular manifest issue, which is about file associations. But it is something we're interested in. -- 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-368771575
Received on Tuesday, 27 February 2018 07:23:30 UTC