[jira] [Commented] (TAP5-2397) AjaxFormLoop / DateField not operable if added by addRow event

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169255#comment-14169255 ] 

Jochen Kemnade commented on TAP5-2397:
--------------------------------------

I just had a quick look. The problem is that the {{t5:zone:did-update}} event is triggered on the AjaxFormLoop's {{insertionPoint}} which does not contain the added content. So the problem will occur with every component that is initialized using {{dom.scanner}}. Should we just trigger the event on the new element? Probably we should even use a new event type for this case - {{t5:zone:did-update}} is not entirely accurate.

> AjaxFormLoop / DateField not operable if added by addRow event
> --------------------------------------------------------------
>
>                 Key: TAP5-2397
>                 URL: https://issues.apache.org/jira/browse/TAP5-2397
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Sven Homburg
>
> After i add a new row to the ajaxformloop, the datefield-component is not operable.
> No action if i click the calander-button but also no javascript error in console.
> All other rows, that injected by the source parameter of ajaxformloop work as expected with the datefield component.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)