Web Writable Files API: Simplifying Local File Access

Re:Web Writable Files API: Simplifying Local File Access by justizin on Monday November 12, 2018 @03:56PM (#18435713)

The ChromeOS browser does not have access to local files, it can download files to a ~/Downloads folder, but it cannot manipulate local files.

The entire point of ChromeOS is aggressive sandboxing, not breaking out of the sandbox.

[ Parent | on HN ]

Re:Web Writable Files API: Simplifying Local File Access by pjmlp on Monday November 12, 2018 @04:12PM (#18435870)

Apparently I can write files in ChromeOS.

https://developer.chrome.com/apps/fileSystem

[ Parent | on HN ]

Re:Web Writable Files API: Simplifying Local File Access by xrd on Monday November 12, 2018 @04:27PM (#18436011)

You get access to this if you have written a Chromebook app. If you get a user to install that, there is a clear set of permissions they are accepting. See the section on permissions, which is specified in the app manifest. It is not an open hole for anything running on a Chromebook.

[ Parent | on HN ]

Re:Web Writable Files API: Simplifying Local File Access by pjmlp on Monday November 12, 2018 @04:58PM (#18436312)

Or a Chrome app, even though they are currently deprecated.

Yes the user needs to install it, and then it is free reign for $HOME.

So it isn't Download location only.

[ Parent | on HN ]