On Mon, November 25, 2013, Martin Grigorov wrote: > > In my project I am experiencing IE8 crashes at (Ajax-based) file > > upload. This happens with some particular machines my client > > uses, and, no, replacing them is (unfortunately) not an option. > > > > Can you explain what is the issue ? > Maybe Wicket can workaround it ...
I'll try to. Since I cannot reproduce the problem myself (on my IE8 the application works just fine), I can hardly describe much more than the symptoms. When uploading a file using an AjaxButton, the browser freezes after the upload has been processed on the server, i.e. the button stays 'pushed', and the browser needs to be closed using the task manager. The action behind my upload button is fully executed, i.e. the upload is being processed successfully, and the components that need Ajax update are added to the onSubmit method's ART. That's the last I see from that browser in the logs. In order to narrow down the problem I've created an upload test page. It contains a simple form with an FileUploadField/AjaxButton in it. Also there is the upload component panel we use in our application (it maintains a list of uploads that are updated via Ajax and shown under the upload button). Last Friday I made the trip to our customer's and took a closer look at one of the machines. All of them are WinXP/IE8 boxes, supposedly with identical configurations, but only some of them exhibit those crashes (but those do this each time we try). When running on Wicket 6.9.12 the browser crashes even with the simplest configuration (FileUploadField/AjaxButton). After downgrading to 6.8.0 (since there once was an issue in the wicket bugtracker), the browser survives that first check, but it crashes when trying out our application's upload component. This leads me to think that there is some Javascript/Ajax stuff involved in this crash. That's about all I know. I may give you access to that test page via email if you like to check yourself. > I am not sure whether you will be able to use AjaxRequestTarget though. > Because the Ajax call is made by the JS library, not with Wicket.Ajax.** > APIs. So it will require some JS coding from you to process <ajax-response> > in the library's onSuccess callback. That's what I feared :) This simply means that I will have to dig deeper into that particular upload library. Since I don't even know whether it will solve my problem I will have to consider... > > Also, are there any other components that I could try? I took a > > look at wicket-uploadify, but that library is based on wicket > > 1.5, and apart from that I haven't found anything. > > > > Is it hard to migrate it to 6.x ? It contains some Javascript that will most likely no longer work. Also it is totally undocumented, I don't know how to use it and if it even works. Actually I went into the same question, how can I notify my application so that I can use it the same way I used to use the stock FileUploadField. Cheers, M'bert -- ----------- / http://herbert.the-little-red-haired-girl.org / ------------- =+= #define S "Goodbye!\n" main(){exit(printf(S) != strlen(S) ? 0 : 1);} --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
