It appears that this fix is already working in 6.11.0-SNAPSHOT.

The fix was committed here:
https://github.com/apache/wicket/commit/bfd4649656f4f51c8d1a164cc14cb5b8dc71f89d

See https://issues.apache.org/jira/browse/WICKET-5315

I applied that change to my code and the auto complete works now.

On 08/27/2013 07:53 AM, Jered Myers wrote:
I added this case to JIRA with a quickstart. It is a critical bug for my company.

https://issues.apache.org/jira/browse/WICKET-5332

Jered

On 08/27/2013 06:39 AM, Sven Meier wrote:
Hi Jan,

autoComplete is a little delicate in the ordering of javascript event registrations, so this might not have any effects on other components.

A quickstart will help to identify the problem.

Sven

On 08/27/2013 03:21 PM, TechDB wrote:
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



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to