[
https://issues.apache.org/jira/browse/TAP5-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340064#comment-14340064
]
Jochen Kemnade commented on TAP5-2457:
--------------------------------------
Can you post some of your code, especially how the content is inserted into the
DOM? I assume you don't use Zones?
The datefield uses {{t5/core/dom:scanner}} to do its client-side
initialization. Currently, that is only triggered for Zone updates.
As a workaround, you can trigger the {{t5/core/events.zone.didUpdate}} event on
the content you insert into the DOM.
> DatePicker and async loaded form
> --------------------------------
>
> Key: TAP5-2457
> URL: https://issues.apache.org/jira/browse/TAP5-2457
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.4
> Reporter: Charles Capon
> Labels: datefield, datepicker
>
> I load a form in a modal asynchronously several time on a single page and the
> datepicker is only working the first time.
> I investigate for a bit and it appears that it is because of requirejs that
> load and run only once the datefield module (which make sense).
> The problem is that on other datefield async loading, the datepicker is not
> initialized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
