On Tue, Jul 23, 2013 at 6:44 PM, Andrew Geery andrew.ge...@gmail.comwrote:
Just to make sure I'm understanding this correctly, it should be enough to
simply override updateAjaxAttributes on AjaxButton and specify a channel
that does not have ACTIVE behavior, like this:
@Override
The problem is the ajax-loader-mask. As per this posting (
http://stackoverflow.com/questions/12403999/jquery-click-event-doesnt-work-after-change-event),
the click happens (but no js click event yet), the js change event is sent
for the modified form field, Wicket handles the change event, the
HI,
Unless you use AjaxChannel.ACTIVE on the AjaxButton you should not
experience this behavior.
It should work exactly as you expect it.
Try to put some debug statements with an AjaxCallListener - print to
console in onBefore() and onBeforeSend(). Add this listener to both
components - the field
Just to make sure I'm understanding this correctly, it should be enough to
simply override updateAjaxAttributes on AjaxButton and specify a channel
that does not have ACTIVE behavior, like this:
@Override
protected void updateAjaxAttributes(AjaxRequestAttributes
attributes) {
Looking in the Wicket Debug Window, I do see the name of my channel and I
do see that it is set to Queue (MyChannel|s).
I have a form that is submitted with an AjaxButton. One of the fields in
the form uses an AjaxFormComponentUpdatingBehavior to update the
server-side state when a value in the field changes (i.e., it fires
onchange). If the user changes the field with
the AjaxFormComponentUpdatingBehavior
