Hello, I can confirm the behavior. It happens on al AutoComplete fields that are added lazy via ajax. The mentioned error in ajax debug "ERROR: Cannot find element with id: null" is produced by the script that tries to add the autocomplete event to the element via header contribution. It seems that the sequence of the evaluation for component adding and header contribution via ajax has changed. Meaning that the autocomplete script is looking for an element that was not added yet.
Does this also break other elements? Jan -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/AutoCompleteTextField-break-in-new-wicket-6-10-0-tp4661085p4661097.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
