[
https://issues.apache.org/jira/browse/TAP5-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345349#comment-14345349
]
Charles Capon commented on TAP5-2457:
-------------------------------------
i fixed it adding by an id and "data-container-type"= "zone" to my dom and
using the addRender(id, renderer) of ajaxResponseRenderer which is way better
than what i did before. It's more tapestry style ;)
Anyway, I want to publish to a tapestry library my work about that because I
think it could benefit to other people. I also think that my code could be
better and others contributions would help me. I have tried to go deep into the
tapestry source to really understand but there are some tricky things that i'm
still not familiar with.
I'll post a mail on the user maling-list ASAP.
> 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)
