W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2013

Re: [whatwg] Forms: <input type=file> and directory tree picking

From: Glenn Maynard <glenn@zewt.org>
Date: Thu, 29 Aug 2013 17:48:11 -0500
Message-ID: <CABirCh_UGOd_rQnP5p+PA0kums_SnKucoMC7XO1jiR38cfEL1Q@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: WHAT Working Group <whatwg@lists.whatwg.org>, Jonathan Watt <jwatt@jwatt.org>, Ian Hickson <ian@hixie.ch>
On Thu, Aug 29, 2013 at 5:06 PM, Jonas Sicking <jonas@sicking.cc> wrote:

> >> We don't have to do any enumeration synchronously. It can all happen off
> >> the main thread. The .click() "API" is asynchronous.
> >
> > It's asynchronous to the JS, sure, but at the end of the day the user
> > can't get any work done until it's complete. It's synchronous as far as
> > the user is concerned.
> Sure. The alternative is that the user attaches each file separately.
> Which, while means smaller "synchronous" actions, is not really a
> better UX. In other words, synchronousness is not the only design
> constraint here.

The alternative is to provide an interface that explores the supplied
directory on-demand, as the page needs it, rather than greedily scanning
the entire directory before giving it to script.  Scanning a large
directory tree in advance is almost never what applications or users want.

A static file list isn't a sensible API for recursively exposing directory

Glenn Maynard
Received on Thursday, 29 August 2013 22:48:37 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:23 UTC