Re: [w3ctag/design-reviews] Files and Directory Entries API with webkit prefixes! (#215)

To clarify: all of @travisleithead's feedback is a **great** reason to not just unprefix `webkitdirectory`.

A plausible incremental path forward building on what browsers have now:
* add a `directory` attribute to HTMLInputElement and expose an `FrozenArray<FileSystemEntry> entries` property which is populated on selection and contains only what was explicitly selected by user, with no extra traversal. If a single file or multiple files are selected, this would be one or more `FileSystemFileEntry`. If a directory is selected it would be a single `FileSystemDirectoryEntry`. (This addresses points 1, 3, 5 and 6)
* add modern async APIs to the interfaces: Promise-based getters, and async iterator support for FileSystemDirectoryReader. (i.e. what the helper examples in the spec do) (This addresses point 4)

(Since Edge doesn't support the methods on the interfaces today this should result in a fairly clean interface in Edge. Other browsers would have both the callback APIs and Promise/async iterator APIs for back-compat.)



-- 
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/215#issuecomment-362424499