Hi,
I see you don't have custom AjaxRequestAttributes, so no custom
preconditions.
Wicket has just one default precondition - it will execute the Ajax call
only if the related HTML element (the link) is in the current document.
That is the point I don't get ... how can an element doesn't exist in DOM but I
can click on it?
Marvin Richter
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, February 06, 2014 3:05 PM
To: users@wicket.apache.org
Subject: Re: Precondition Check
in DOM
but I can click on it?
Marvin Richter
-Original Message-
From: Martin Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, February 06, 2014 3:05 PM
To: users@wicket.apache.org
Subject: Re: Precondition Check
Hi,
I see you don't have custom AjaxRequestAttributes, so
@wicket.apache.org
Subject: Re: Precondition Check
you can click on it and the event listener can delay the actual Ajax call as
much as it wants (Wicket's AjaxChannel.QUEUE does exactly this).
E.g. click two times on the link, the first click fires Ajax call (the second
click waits), its response removes
: Thursday, February 06, 2014 3:22 PM
To: users@wicket.apache.org
Subject: Re: Precondition Check
you can click on it and the event listener can delay the actual Ajax call
as much as it wants (Wicket's AjaxChannel.QUEUE does exactly this).
E.g. click two times on the link, the first click fires
Grigorov [mailto:mgrigo...@apache.org]
Sent: Thursday, February 06, 2014 3:40 PM
To: users@wicket.apache.org
Subject: Re: Precondition Check
So the check fails here
https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-ajax-jquery.js?source=c#L511
