3 ms·
This is not access to the filesystem. This is access to some controlled contents that happen to come from the filesystem, with interaction explicitly initiated
by nine_k 4y ago
This is not access to the filesystem.
This is access to some controlled contents that happen to come from the filesystem, with interaction explicitly initiated by the user every time. It gives the browser no access to the structure of the filesystem, no way to navigate it, and crucially no way to transparently read or write anything.
This is good isolation, I'd prefer it to be this way. OFS also gives equally good isolation, I'm fine with that.
Sharing between OFS and the rest of the user's file system should be possible, but only explicitly, a la iOS, Android, and the file upload / download dialog.
- cxr 4y agoPlease follow the discussion; we are not referring to the narrow "origin private file system" here. > This is not access to the filesystem. Wrong. I know what "this" is, thanks, and it is access to the filesystem. That's because "this" here—in the subthread you have just posted to—refers to Chrome's experimental implementation of the larger proposal (which is literally called "File System Access API"), not the limited subset described by the submission as having just gotten enabed in Firefox.
- nine_k 4y agoPlease take another look at the comment I was replying to. It was about <input type="file"> and <a> with disposition attribute, which are not filesystem access. While Google's new API definitely is.
- cxr 4y ago> Please take another look at the comment I was replying to. It was about <input type="file"> and <a> with disposition attribute It's the `download` attribute, but yeah, I understand the significance of those words. I wrote them. Your replies in this thread, on the other hand, are confusing at best. What are you actually trying to communicate?