[jira] [Commented] (TAP5-2457) DatePicker and async loaded form

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

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

Jochen Kemnade commented on TAP5-2457:
--------------------------------------

I hope you were able to fix your issue. I still wonder how to solve that kind of problems. Maybe {{dom:scanner}} should not be wired to the {{t5/core/events.zone.didUpdate}} event (see also TAP5-2397). We could call it at the end of the {{ElementWrapper}} mutator methods (e.g. {{update}}), but that wouldn't help users who like to modify their DOM with raw jQuery/Prototype/whatever JS provider. I think a custom {{t5/core/events.dom.contentChanged}} event would be the best option. [~hlship], any thoughts?
{quote}
I could show you what am I doing if you want to.
{quote}
If you don't mind, I'd be interested. I've had a go at a Modal component some time ago, but didn't get very far. I'd like to see your approach.

> 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)