You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juha Paananen (JIRA)" <ji...@apache.org> on 2010/03/05 10:52:27 UTC
[jira] Updated: (WICKET-2424) OnChangeAjaxBehavior + DatePicker do
not work together
[ https://issues.apache.org/jira/browse/WICKET-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juha Paananen updated WICKET-2424:
----------------------------------
Attachment: wicket-2424-patch.txt
Patch to fix the issue. Created for wicket-1.4.6.
> 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
> Priority: Minor
> 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.