You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Janne Hietamäki (JIRA)" <ji...@apache.org> on 2007/03/23 09:33:32 UTC
[jira] Resolved: (WICKET-378) autocomplete does not explicitly call
input's onchange event
[ https://issues.apache.org/jira/browse/WICKET-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Janne Hietamäki resolved WICKET-378.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.3
1.2.6
> autocomplete does not explicitly call input's onchange event
> ------------------------------------------------------------
>
> Key: WICKET-378
> URL: https://issues.apache.org/jira/browse/WICKET-378
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.2.5
> Reporter: David R Robison
> Assigned To: Janne Hietamäki
> Fix For: 1.2.6, 1.3
>
>
> When selecting a item from the autocomplete drop down, the onchange event handler on the input is not called. The wicket-autocomplete.js needs to be modified to call the onchange function explicitly. the changes should include:
> case KEY_ENTER:
> if(selected>-1){
> obj.value=getSelectedValue();
> if (typeof obj.onchange == "function") obj.onchange ();
> hideAutoComplete();
> return killEvent(event);
> }
> return true;
> break;
> and
> node.onclick = function(event){
> wicketGet(elementId).value=getSelectedValue();
> if (typeof wicketGet(elementId).onchange == "function") wicketGet(elementId).onchange();
> hideAutoComplete();
> }
> Thanks, David
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.