On Fri, Mar 15, 2013 at 10:15 AM, Tom Evans <tevans...@googlemail.com> wrote: > I'm > fairly certain that <input type="file"> should not throw any change > events or make the name of the file available to JS, for reasons of > security.
it does generate change events, even if the value is a black box. > Auto submitting the form would not allow the user to correct > mistakenly selecting the wrong file, or rather, forms usually allow > you to change a field and verify before submitting i agree that it's rude to submit a form before the user explicitly 'sends' it; but this behaviour is appearing more and more. the idea is that the upload happens while the user fills other fields. the uploaded file isn't "confirmed" yet, it would be replaced if the user chooses another one on the same 'slot' (if there are multiple 'choose file' fields). if the user 'cancels' the form, the uploaded file should be discarded. this doesn't mix too well with the multiple="true" attribute.... it's not an easy answer because of the many different user expectations. -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
