[
https://issues.apache.org/jira/browse/WICKET-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Bille Jensen updated WICKET-488:
--------------------------------------
Fix Version/s: (was: 1.4-M1)
1.4-M2
> Allow more complex behaviour for AutoCompleter component
> --------------------------------------------------------
>
> Key: WICKET-488
> URL: https://issues.apache.org/jira/browse/WICKET-488
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-extensions
> Environment: wicket-1.x snapshot
> Reporter: Peter Ertl
> Fix For: 1.4-M2
>
> Attachments: autocomplete-on-select-including-onclick.patch,
> autocomplete-on-select.patch, jquery.js,
> WICKET488_MoreComplexBehaviorForAutocompleter.patch
>
>
> It would be nice to be able to modify the default behaviour of the ajax
> autocompleter component upon selection of an list item. this would make it a
> even more useful component and exceed it's capabilities beyond simple text
> replacement.
> current behaviour:
> ### snip : wicket-autocomplete.js line 93-97 ###
> case KEY_ENTER:
> if(selected>-1){
> obj.value=getSelectedValue();
> hideAutoComplete();
> hidingAutocomplete=1;
> ### eof snip ###
> Instead of having obj.value= being filled by the current text value it would
> be nice to have the option of specifying a js function callback to e.g. post
> back the selected value to the server. This way you could implement more
> complex behaviour, for example select a company address from a list and, on
> selecting it, send back the address id to the server which then would fill
> out street, house number, zip code and city.
> pseudo code:
> if selected
> if callback
> callback(value)
> else
> obj.value = current value
> end
> .....
> probably the right place for such a on-select contribution would be the
> autocomplete renderer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
