tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-2124) events.zone.refresh must be triggered directly on zone element, can fail otherwise
Date Sat, 29 Jun 2013 17:15:20 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-2124.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4
         Assignee: Howard M. Lewis Ship
    
> events.zone.refresh must be triggered directly on zone element, can fail otherwise
> ----------------------------------------------------------------------------------
>
>                 Key: TAP5-2124
>                 URL: https://issues.apache.org/jira/browse/TAP5-2124
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.4
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>              Labels: javascript, zone
>             Fix For: 5.4
>
>
> Triggering the events.zone.refresh or events.zone.update events on an element nested
within a Zone's element will fail; the document-level event handlers expect this to be the
ElementWrapper for the zone element, but is instead the ElementWrapper for the triggering
element.
> Currently, it is necessary for triggers to select up the tree to find the Zone's element;
this should be incorporated into the document event handlers instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message