sorry, i try to be more specific. after moving to wicket 6.10.0, it fails in
two different cases:
case 1: when adding this behavior:
autoComplete.add(new AjaxFormComponentUpdatingBehavior("onKeyUp") {
@Override
protected void onUpdate(final AjaxRequestTarget target) {
...
}
}
without it, it works fine. this code works fine up to wicket 6.9.1.
case 2: no behaviors at all, still to be determined the problematic point;
just multiple auto-completes on the view and wicket-ajax-debug complaining
many times with output "ERROR: Cannot find element with id: null" (not clear
yet it this has to be with the problem in the auto-complete, but these
errors where not happening before in wicket 6.9.1).
thx
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/AutoCompleteTextField-break-in-new-wicket-6-10-0-tp4661085p4661088.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
