Re: [w3ctag/design-reviews] Native File System API (#390)

I did a review of the spec today and found this linked in an issue, so I thought I'd summarize what seem like the most important existing or new issues to me.

On API shape:
- [Why not use ReadableStream/WritableStream/WritableStream*Writer](https://github.com/WICG/native-file-system/issues/19)
- [Async iterables are happening](https://github.com/WICG/native-file-system/issues/47)
- [Consider renaming FileSystemDirectoryHandle's getFile() method to getFileHandle()](https://github.com/WICG/native-file-system/issues/98)
- [Provide append functionality](https://github.com/WICG/native-file-system/issues/114) / [Let write() resolve with the number of bytes written?](https://github.com/WICG/native-file-system/issues/124) (bugs seem likely)

On behavior/interoperability:
- [Interoperability of security and privacy considerations](https://github.com/WICG/native-file-system/issues/136)
- [When is user activation / prompting required?](https://github.com/WICG/native-file-system/issues/120)
- [How do MIME types map to native file systems?](https://github.com/WICG/native-file-system/issues/133)
- [Handling of non-Unicode handle names](https://github.com/WICG/native-file-system/issues/115) / [symlinks](https://github.com/WICG/native-file-system/issues/113)

Finally, [cloud drive considerations](https://github.com/WICG/native-file-system/issues/123) are *probably* not a big deal, but could affect the shape/behavior of the API given feedback from experts on that.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/390#issuecomment-556017791