igor.vaynberg wrote: > > weird, you will have to debug and see what is happening. > > a good place to start is Form#onFormSubmitted() > > -igor > Thanks for the tip, Igor.
I have tried this, and my Form#onFormSubmitted() method is only called if the FileUploadField field does not have an empty file selected. However, I have found that my results depend on the internet browser used. Using Mozilla Firefox (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)) I get the blocking activity that I have already described (form submission requests by submit components do not result in component or form submission). Using Microsoft Internet Explorer 8 (version 8.0.6001.18702) all works fine and an empty file does not block processing in any way. I shall have to proceed, but I do not know whether my problem is a true bug of Wicket or not. I have tried file upload components from other web sites on Firefox and this problem does not arise. I am not a developer of the Wicket framework. Is there any way I can submit this behaviour as a potential bug for someone else to verify or not? Thanks again for your questions and pointers anyway. Ian Marshall -- View this message in context: http://www.nabble.com/FileUploadField-blocks-component-submission-when-an-empty-file-is-selected-tp25855504p25871355.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
