wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Heigl <tho...@umschalt.com>
Subject Re: Ajax file upload broken in IE8 with Wicket 6.9.0
Date Tue, 23 Jul 2013 13:08:37 GMT
Hey Martin,

The example works fine.

I just tried to narrow the problem down and found that the root cause is
using AjaxFormSubmitBehavior("onchange") on the input field. The absolute
minimal example that crashes my IE8/XP on the first or second upload is:

public class TestPage extends WebPage {
> public TestPage(PageParameters pp) {
> super(pp);
> final Form<Void> f = new Form<Void>("form");
> f.setMultiPart(true);
> add(f);
> final FileUploadField uploadField = new FileUploadField("fileInput", new
> ListModel<FileUpload>());
> uploadField.add(new AjaxFormSubmitBehavior("onchange") {});
> f.add(uploadField);
> }
> }


<html xmlns="http://www.w3.org/1999/xhtml" xmlns:wicket="
> http://wicket.apache.org/dtds.data/wicket-xhtml1.4-strict.dtd">
> <body>
> <form wicket:id="form">
>     <input type="file" wicket:id="fileInput" />
> </form>
> </body>
> </html>


Hope that helps to track the problem down.

Thomas




On Tue, Jul 23, 2013 at 1:42 PM, Martin Grigorov <mgrigorov@apache.org>wrote:

> Hi,
>
> Just tested wicket-examples 6.0-SNAPSHOT -> Ajax -> File Upload Example and
> it works OK on Windows XP / IE 8.
> I'll upload 6.9.1 to
> http://www.wicket-library.com/wicket-examples-6.0.x/ajax/upload?1 so you
> can test there
>
>
> On Tue, Jul 23, 2013 at 2:30 PM, Thomas Heigl <thomas@umschalt.com> wrote:
>
> > Hey all,
> >
> > After upgrading to Wicket 6.9.0 our ajax file upload started stalling and
> > on some machines even crashing IE8. Downgrading to 6.8.0 immediately
> fixed
> > the problem.
> >
> > I verified that the issue is not related to the new jQuery version by
> > downgrading to Wicket 6.8.0 but setting the jQuery resource reference to
> > 1.10.1. File upload still works in that case.
> >
> > I browsed the history of wicket-ajax-jquery.js since 6.8.0 but didn't
> find
> > anything too suspicious.
> >
> > Does anyone have any idea what could cause the problem or is experiencing
> > the same issues?
> >
> > I can try to create some kind of quickstart if that helps.
> >
> > Cheers,
> >
> > Thomas
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message