So I figured out that what's happening is that evidently wicket 6 doesn't put
the javascript inline, but uses event listener registration or whatever.
And it seems like this overwrites my inline event in an AjaxButton. The
solution:
@Override
protected void
updateAjaxAttributes(AjaxRequestAttributes attributes) {
super.updateAjaxAttributes(attributes);
AjaxCallListener listener = new
AjaxCallListener();
listener.onPrecondition("return copyClick();");
attributes.getAjaxCallListeners().add(listener);
}
However, no sooner do I solve this, then I find that one of my submit
buttons (which is just a new Button, not AjaxButton) is having a similar
problem. But the above method does not exist on mere Button. How can I do
something similar?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AjaxButton-does-not-respect-return-false-on-client-side-tp4665497p4665498.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
