tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Massimo Lusetti (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1949) Alerts component does not show alerts added from a component that occurs later in the template
Date Tue, 12 Jun 2012 08:13:44 GMT

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

Massimo Lusetti commented on TAP5-1949:
---------------------------------------

I like the proposed behavior. Did anyone see a draw back in this changes?
                
> Alerts component does not show alerts added from a component that occurs later in the
template
> ----------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1949
>                 URL: https://issues.apache.org/jira/browse/TAP5-1949
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.3, 5.4
>            Reporter: Jochen Kemnade
>            Priority: Minor
>              Labels: patch
>         Attachments: 0001-defer-the-alerts-JS-initialization-to-allow-for-aler.patch
>
>
> Consider the following snippet:
> <t:alerts />
> <t:componentthataddsanalert />
> The alert will not be shown as the JS for the alerts is generated in the beginRender
phase of the alerts component. and alerts that are added later are ignored until its next
rendering.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message