I must admit that I don't know their workflow. But I guess that it is far heavier and time-consuming than that of Wicket, right? Could you please see if you can find a work-around?
What I'm afraid of, is that they could say: "we know nothing about your Wicket thing, we support GWT and Angular.js, so please go back home", if you know what I mean... Regards, Pierre On Wed, Jan 30, 2013 at 9:24 PM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > Did you create a bug report at chrome? Sounds like a bug in their > browser rather than in wicket. > > Martijn > > On Wed, Jan 30, 2013 at 9:00 PM, Pierre Goupil <goupilpie...@gmail.com> > wrote: > > Good evening, > > > > I've been through a strange behavior since I upgraded my Linux box to > > Chrome 24 (latest stable release, I believe). > > > > To put it shortly, the Ajax links reload the page, hence their actions > are > > mostly not taken into account. > > > > I've created: > > > > https://issues.apache.org/jira/browse/WICKET-5015 > > > > and attached a quickstart to prove it. > > > > FYI, the bug is not present in Firefox or Opera. > > > > Hope to hear from you soon, guys! > > > > Regards, > > > > Pierre > > > > > > > > -- > > "Parce que c'est la nuit qu'il est beau de croire à la lumière." > > > > Edmond Rostand > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- "Parce que c'est la nuit qu'il est beau de croire à la lumière." Edmond Rostand
