[
https://issues.apache.org/jira/browse/TAP5-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340078#comment-14340078
]
Charles Capon commented on TAP5-2457:
-------------------------------------
It's true that i'm not using zone. My app uses lots of bs modal. In order to
only have one modal, I setup a Modal component and a ModalSupport service.
The ModalSupport adds the dom for a single modal at the end of the html body
and modal component are render only when needed (before showing them).
I could show you what am I doing if you want to. As for now, i'll try to adapt
my code and use zone instead of my specific code (or just send a zone.didUpdate
event if it's too complicated)
> 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)
