On Tue, 6 Apr 2010, Tab Atkins Jr. wrote: > > The proposal is to mandate that <input type=search> expose some sort of > "clear" widget in itself, which fires an appropriate event when the user > activates it.
It already does -- the event is "input" and in the case you describe, it would fire with value == "". > [<input type=directory> vs <input type=file multiple>] > > The advantages are precisely what was listed in the email - a proper > directory uploader with path information for the files (either baked > into the filename or available separately) allows you to: > > 1. Easily accept multiple files with the same name, as long as they're > in different directories (this restriction is already enforced in all > major OSes) > > 2. Maintain the directory structure the user uploaded, for example a > pictures directory with folders for "vacation" and "wedding" photos > separate. > > 3. Expose the most appropriate UI to the user - in most file selection > dialogs you are *unable* to select a folder itself. In the few that > allow it, it is often difficult to discover the functionality. OSes > do provide a proper directory picker, though, which is much more clear > about what it does. It seems like it should be up to the user whether to be able to select a directory or not. We could maintain the relative path information easily (just include the paths under C:\FAKEPATH\). -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'