You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Michael Wyraz (Commented) (JIRA)" <ji...@apache.org> on 2012/02/10 12:49:59 UTC
[jira] [Commented] (TAP5-1844) Datefield not fires onchange event
on changes
[ https://issues.apache.org/jira/browse/TAP5-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205371#comment-13205371 ]
Michael Wyraz commented on TAP5-1844:
-------------------------------------
To fix this, in datefeild.js change
this.field.value = result;
to:
if (this.field.value != result) {
this.field.value = result;
if (this.field.onchange) this.field.onchange();
}
> Datefield not fires onchange event on changes
> ---------------------------------------------
>
> Key: TAP5-1844
> URL: https://issues.apache.org/jira/browse/TAP5-1844
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.1
> Reporter: Michael Wyraz
>
> It's a "regression" to TAPESTRY-238
> in datefield.js when setting the field's value, onchange() must be called if it exists
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira