We haven't used 1.4.11, so it comes from upgrading from 1.4.8 straight to 1.4.12
I'm no good at javascript at all, but I will see what I can reproduce with a quickstart when I get time. But for now we'll stick with 1.4.8 in production. On Sun, Oct 3, 2010 at 12:48 PM, Martin Grigorov <[email protected]> wrote: > Did you try with 1.4.11 before trying 1.4.12 ? > Someone in IRC had the same problem - try 1.4.11, the browser caches the > broken wicket-ajax.js (see WICKET-3040) and then upgrade to 1.4.12 but the > browser still used the cached version from 1.4.11. > > You said that you tried several browsers so maybe it is not the same case. > Many people use 1.4.12 and they don't experience this problem... > > On Sun, Oct 3, 2010 at 12:32 PM, Mathias Nilsson < > [email protected]> wrote: > >> >> I also tried 1.4.12 and got the same problem in chrome. >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-12-Ajax-problems-tp2930684p2953070.html >> Sent from the Users forum mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
