<div class="gmail_quote">On Fri, Apr 23, 2010 at 8:41 PM, Anne van Kesteren <span dir="ltr"><<a href="mailto:annevk@opera.com">annevk@opera.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, 23 Apr 2010 07:11:08 +0900, Ojan Vafai <<a href="mailto:ojan@chromium.org" target="_blank">ojan@chromium.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But there is already a default UI that lets you select a folder, a file or both (drag-drop). I don't see why this forces the UA to do anything. Just<br>
because you can select both folders and files doesn't mean the UA needs to expose extra UI on top of drag-drop to let you do so. Again, no more so than they already have to expose extra UI to deal with multiple inputs.<br>
</blockquote>
<br></div>
How does the drag & drop API support this use case?</blockquote><div><br></div><div>I'm not sure I understand the question. Are you suggesting that for cases where people want to support directory+file drops they should use drag-drop instead of an input element?</div>
<div><br></div><div>My point is more that input elements currently support dropping files onto them in multiple browsers. It's confusing for "multiple" that dropping directories+files doesn't upload said directories+files, or at least give some sort of indication to the user that some of them are being not allowed.</div>
<div><br></div><div>We should leave it up to UAs to figure out what the right UI should be, but adding input "directory" seems to me like it will confuse the UI more. Ideally users can drop whatever they want onto a file input that has "multiple" and it can be up to the web page to remove entries it doesn't allow. The web page is in a much better position to give user feedback (e.g. a photo site can warn that only image uploads are allowed and that non-images won't get uploaded).</div>
<div><br></div><div>Ojan</div></div>