[
https://issues.apache.org/jira/browse/WICKET-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2424.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
1.4.8
Assignee: Igor Vaynberg
> OnChangeAjaxBehavior + DatePicker do not work together
> ------------------------------------------------------
>
> Key: WICKET-2424
> URL: https://issues.apache.org/jira/browse/WICKET-2424
> Project: Wicket
> Issue Type: Bug
> Components: wicket, wicket-extensions
> Affects Versions: 1.4.0
> Environment: Firefox, IE
> Reporter: Alexey Varlamov
> Assignee: Igor Vaynberg
> Priority: Minor
> Fix For: 1.4.8, 1.5-M1
>
> Attachments: wicket-2424-patch.txt
>
>
> DatePicker fails to notify component update when OnChangeAjaxBehavior is used
> on the target input.
> It works well with AjaxFormComponentUpdatingBehavior.
> The root cause seems to be in the Wicket.ChangeHandler added by the
> OnChangeAjaxBehavior, which hides user handler while the DatePicker calls
> onchange handler directly (wicket-date.js:186):
> if (field.onchange != null && typeof(field.onchange) != 'undefined')
> field.onchange();
> Possible fix could be dispatching onchange Event instead of direct handler
> invocation.
> Yet I don't know what is purpose of Wicket.ChangeHandler here...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
