Hello, Thank you for your replies.
The wicket versions I'm using for the applications are 1.3.0beta4, 1.3.1, 1.3.2. I know all of them are pretty old but so are the deployed applications. I have no wicket console available - I cannot put the applications in debug mode as those are already in production. No errors are being displayed by firefox. It just doesn't work. I tried the link given by jWeekend and it works so I suspect theres a conflict with 2.0.0.18 the wicket versions I was using. Sorry for the lame way I asked the question yesterday but it was already very late here... Cristi Manole On Mon, Nov 17, 2008 at 1:44 AM, jWeekend <[EMAIL PROTECTED]>wrote: > > Cristi, > > We have just upgraded to 2.0.0.18 on one of our machines and all the AJAX > on > http://jweekend.com/dev/BookingPage/ this page works fine. > Try that link and if it fails to work check Tools/Options/Content to ensure > JavaScript is enabled. > > Regards - Cemal > http://www.jWeekend.co.uk http://jWeekend.co.uk > > > > Cristi Manole wrote: > > > > Hello, > > > > Since Firefox automatically updated to 2.0.0.18 every ajax I had in the > > application (for instance ajax link / button) stopped working if it > didn't > > have fallback. > > > > The applications I have are all in production so this is very annoying. > In > > Internet Explorer all work. > > > > Did anybody else experience this? Is there a workaround? > > > > Thank you, > > Cristi Manole > > > > > > -- > View this message in context: > http://www.nabble.com/Firefox-2.0.0.18-tp20531316p20531584.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
