- From: Jonas Sicking <jonas@sicking.cc>
- Date: Sun, 4 Aug 2013 22:55:15 -0700
- To: Glenn Maynard <glenn@zewt.org>
- Cc: whatwg <whatwg@lists.whatwg.org>, Jonathan Watt <jwatt@jwatt.org>
On Sun, Aug 4, 2013 at 4:54 PM, Glenn Maynard <glenn@zewt.org> wrote: > On Sun, Aug 4, 2013 at 2:47 AM, Jonas Sicking <jonas@sicking.cc> wrote: >> >> We can't do what you are suggesting for a plain <input type=file >> multiple> since there's already a defined API for that, and that API >> only exposes a .files property in the DOM. > > Sure we can; we can always add to that API, such as adding a getFileSystem() > method. A different @type may be better anyway, though. We would also have to expose all files in the selected directory through HTMLInputElement.files, which brings the performance issues that Jonathan is talking about. >> But we could certainly add some way to enable creating an <input> >> which exposes files and directories in the DOM, rather than just >> files. Doing that will depend on coming up with a filesystem proposal >> which all parties actually agree on implementing, so far we don't have >> such a proposal. > > Unless we think it won't ever happen, it'd be better to keep working towards > that than to rush things and implement greedy recursion. Help welcome. / Jonas
Received on Monday, 5 August 2013 05:56:11 UTC