That's weird men! In wicket-library.com the Ajax links work, except that
you must click once on the first increment button before it works. But in
my quickstart, nothing happens...
I've updated my Chrome version from 24.0.1312.56 to 24.0.1312.57 and the
symptom is the same.
I can see no
It looks like your chrome is somehow broken.
Try to clean whatever can be cleaned and try again.
Or just create a new unix user and try with the same Chrome installation.
On Thu, Jan 31, 2013 at 1:48 PM, Pierre Goupil goupilpie...@gmail.comwrote:
That's weird men! In wicket-library.com the
Men... I've deleted ~/.cache/google-chrome ~/.config/google-chrome. I've
fully de-installed Chrome in Synaptic. I've re-installed it from Google's
official source. And... it works...
Sorry for the noise, I'll close my bug.
I'm a bit puzzled by such a behavior but you know... Is computer science
Is it ubuntu?
---rob
Sent from my phone...excuse any typos.
On Jan 31, 2013 8:32 AM, Pierre Goupil goupilpie...@gmail.com wrote:
Men... I've deleted ~/.cache/google-chrome ~/.config/google-chrome. I've
fully de-installed Chrome in Synaptic. I've re-installed it from Google's
official
No, Debian.
On Thu, Jan 31, 2013 at 2:45 PM, Robert O'Connor robby.ocon...@gmail.comwrote:
Is it ubuntu?
---rob
Sent from my phone...excuse any typos.
On Jan 31, 2013 8:32 AM, Pierre Goupil goupilpie...@gmail.com wrote:
Men... I've deleted ~/.cache/google-chrome
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:
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
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, Wicket 6.5.0 works in IE, FF, Safari and Chrome 23. Now you
install Chrome 24 and it stops working, and that is Wicket's problem?
Chrome is a fricking browser, it supports the web. Wicket is part of
the web, and its javascript is nothing special (i.e. based on jquery).
Chrome apparently
Please try the Ajax examples at:
http://www.wicket-library.com/wicket-examples-6.0.x/ajax/links to see
if they work. Chrome 24 on OS X does work as advertised.
Martijn
On Wed, Jan 30, 2013 at 9:42 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
So, Wicket 6.5.0 works in IE, FF, Safari
Maybe I could investigate on jQuery? If they have an open bug or a
work-around? After all, one of its principles is to abstract you from
browsers différences. What do you think? I really need a hand...
Le 30 janv. 2013 21:43, Martijn Dashorst martijn.dasho...@gmail.com a
écrit :
So, Wicket
I think it is an issue of either your chrome installation (try
re-installing) or a bug is introduced in chrome 24 for linux, as it
doesn't affect chrome 24 running on OS X, and as you say, chrome 23
did work.
Reinstall chrome, see if it works, otherwise file a bug report with
chrome developers
OK, I'll do that and come again when I have more news. Thanks!
On Wed, Jan 30, 2013 at 9:53 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
I think it is an issue of either your chrome installation (try
re-installing) or a bug is introduced in chrome 24 for linux, as it
doesn't
Ajax works fine in my apps with Chrome 24, 25 and 26. OS: Ubuntu.
I'll check your quickstart tomorrow.
Please test at wicket-library.com, as Martijn requested.
On Wed, Jan 30, 2013 at 9:59 PM, Pierre Goupil goupilpie...@gmail.comwrote:
OK, I'll do that and come again when I have more news.
14 matches
Mail list logo
