[
https://issues.apache.org/jira/browse/WICKET-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447616#comment-13447616
]
Martin Grigorov commented on WICKET-4705:
-----------------------------------------
The only to solve this that I see is to make AutoCompleteTextField itself
Ajax-aware, i.e. add an config setting that will say whether the newly selected
value should be send to the server. This way there wont be a need to add
AjaxFormComponentUpdatingBehavior at all.
Otherwise you can use https://github.com/ivaynberg/wicket-select2. Works better
and looks better.
> AutoCompleteTextField + AjaxFormComponentUpdatingBehavior "onchange" problem
> on wicket 6.0
> ------------------------------------------------------------------------------------------
>
> Key: WICKET-4705
> URL: https://issues.apache.org/jira/browse/WICKET-4705
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 6.0.0-beta3
> Environment: macox, chrome, firefox
> Reporter: Diego Fincatto
> Attachments: ACTest.zip
>
>
> I have an AutoCompleteTextField with one
> AjaxFormComponentUpdatingBehavior added and, on wicket 6.0, it stop
> working. It was working perfectly on wicket 1.5.7.
> When I select on value with keyboard, nothing happens. When I click in
> some option, the event is fired twice.
> I attached a quickstart with the problem. Changing the wicket version
> to 1.5.7, everything works ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
