Hi, As far as I know there was no intentional change for this functionality. I haven't had time to debug both quickstarts but a quick check in the code doesn't explain the behavior in 1.5.
See wicket-autocomplete.js, lines 168-184, this is the code that handles KEY_ENTER and there is no usage of killEvent(event), while this function is used in the above switch cases. The same is in Wicket 6.0 where we use jQuery's jqEvent.stopPropagation instead. You can try to debug what happens and explain here. Or you can attach the quickstarts in a new ticket in our Jira and someone of us will do it. On Mon, Nov 5, 2012 at 1:21 PM, <[email protected]> wrote: > Hello wicket community, > > i currently migrate a wicket 1.5 application to wicket 6.2.0 and thereby > face a problem with the AutoCompleteTextField. > consider the following setup: > a page with a Form, AutoCompleteTextField, various other TextField[s] and > a button > > in wicket 1.5 the user could select a choice in the AutoCompleteTextField > by hitting the enter-key - no form submit. > if the user selects a choice in the AutoComplete TextField by hitting the > enter-key in wicket 1.6 the form gets submitted. > > note: the behaivor is identical (aka no form submit) if no button is added > to the form. > > my question is: was this change intentional? if so, how can i achieve the > old behavior? > > i have added two quickstarts (wicket 1.5.8 and 6.2.0) which are based on > the wicket-examples AutoCompletePage, to demonstrate the different handling > and my use case. > > kind regards > > marcel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
