RE: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-12 Thread Chris Colman
or not. -Original Message- From: vladimir.kovalyuk [mailto:koval...@gmail.com] Sent: Saturday, 11 September 2010 8:35 PM To: users@wicket.apache.org Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x You're not alone. I upgraded to wicket 1.4.11 and noticed

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-12 Thread Martin Grigorov
: vladimir.kovalyuk [mailto:koval...@gmail.com] Sent: Saturday, 11 September 2010 8:35 PM To: users@wicket.apache.org Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x You're not alone. I upgraded to wicket 1.4.11 and noticed that the ajax handling was broked. Rolled

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-11 Thread vladimir.kovalyuk
You're not alone. I upgraded to wicket 1.4.11 and noticed that the ajax handling was broked. Rolled back to 1.4.10 and ajax handling was broken. Ctrl+R in FF helped. Probably something is wrong in wicket-ajax.js? -- View this message in context:

Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread MONZON Jose
Hi there! I've been giving a Try to Wicket framework. But I have to admit that I'm starting to get crazy! Some help appreciated. I'm using last Wicket distribution 1.4.11 And I'm trying to implement the Wicket Form (with ajax) example you can find here:

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Andrea Del Bene
MONZON Jose jose.monzon at efgfp.com writes: Hi there! I've been giving a Try to Wicket framework. But I have to admit that I'm starting to get crazy! Some help appreciated. I'm using last Wicket distribution 1.4.11 And I'm trying to implement the Wicket Form (with ajax) example you

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Andrea Del Bene
Hi Jose, I can confirm this bug. It works fine with Wicket version 1.4.8. I will open a bug on Apache JIRA. Sh**! Sorry, but know it seems to work also version 1.4.11. What jars have you inserted in your classpath to run test code?

RE: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread MONZON Jose
2010 13:31 To: users@wicket.apache.org Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x Hi Jose, I can confirm this bug. It works fine with Wicket version 1.4.8. I will open a bug on Apache JIRA. Sh**! Sorry, but know it seems to work also version 1.4.11. What

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Predrag Spasojevic
[mailto:andrea.on@libero.it] Sent: Freitag, 10. September 2010 13:31 To: users@wicket.apache.org Subject: Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x Hi Jose, I can confirm this bug. It works fine with Wicket version 1.4.8. I will open a bug on Apache JIRA. Sh

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Martin Grigorov
1.4.11 seems to have Ajax support broken under Firefox 3.6.x Hi Jose, I can confirm this bug. It works fine with Wicket version 1.4.8. I will open a bug on Apache JIRA. Sh**! Sorry, but know it seems to work also version 1.4.11. What jars have you inserted in your

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread Andrea Del Bene
Martin Grigorov mgrigorov at apache.org writes: Please create a minimal application (quickstart) and attach it to Jira ticket. On Fri, Sep 10, 2010 at 2:45 PM, Predrag Spasojevic predrag.spasojevic at gmail.com wrote: I have the same problem with AjaxButton, wicket 1.4.11 and FireFox

Re: Wicket 1.4.11 seems to have Ajax support broken under Firefox 3.6.x

2010-09-10 Thread nmetzger
I'm glad I'm not the only one. I had a couple of AJAX components not reacting with 1.4.11, no error message though. They worked well with all versions between 1.4.7 and 1.4.10. Natalie -- View this message in context: